text:
Merge 'drug transmembrane transporter' into 'xenobiotic transmembrane transporter' (and the corresponding processes)

This is a splitting out of a single action from #14626
The proposal is to obsolete drug transmembrane transporter. The rationale is that this does reflect a particular mechanism, add the distinction between whether a particular case of transmembrane transport for a chemical constitutes a non-drug or drug transport is either difficult to determine or does not reflect a mechanistic difference. The use of the term drug may have been a proxy for a more mechanistic description: xenobiotic, efflux pump, ...
However, obsoletion of a high level term should be done with consideration to end-users and curators.
I suspect many people search on this term. A clinical or basic researcher may want to search GO for genes involved in drug resistance. We should think through these use cases and determine (a) is GO the appropriate resource for answering this in whole or part and (b) how can we best satisfy this use case? This may involve trying to intuit the intent behind these queries and redirecting them (e.g. via synonyms).
If we agree to obsolete then we should decide if it is (a) a merge or (b) obsolete + replace/consider. I would strongly favor the latter, as I think we want to have clear information for people who do search on this and other drug concepts (e.g. "this terms was obsoleted because ... you may want to consider ..."). I think non-exact synonyms to the alternate terms may be justified.
We have >80 experimental annotations to this. There may be more information in these than simply "chemical transport". The curator may have used "drug transporter" even though a more appropriate mechanistic term was available.
Here is a sample of some existing annotated publications and my non-expert non-curator perspective:
This paper "involvement of an active efflux system in the natural resistance of Pseudomonas aeruginosa to aminoglycosides"
http://amigo.geneontology.org/amigo/reference/PMID:10543738
resulted in 4 annotations directly to drug transmembrane transport(er).
I think the role here is toxin, not drug. The evolved function/mechanism is efflux I think? We have GO:0015562 ! efflux transmembrane transporter activity, is this a better choice of term? (Amelia made this term, so it predated the annotations which were made in 2016!)
Similar for these candida annotations in 2014
http://amigo.geneontology.org/amigo/reference/PMID:8031026
I think the BENr gene is a pump so again seems like the function is pumping stuff harmful to the organism outside the cell? We should also think of the end user here, what kinds of queries would they ask that should meaningfully lead to this gene? E,g searches for "drug resistance" or "drug transport" than "efflux" or "pump". This could be handled with synonyms.
These annotations seem to be annotating to the name of the gene family rather than the function?
http://amigo.geneontology.org/amigo/reference/PMID:9483795

Definitely obsolete and reannotation (80 is a small number to fix, especially spread across resources), all can likely be annotated better, or fixed, and as you say many are toxins. It's more important to know influx or efflux in this situation!
We could, after obsoletion make these labels related  (or narrow) synonyms to "transmembrane
transporter" for searching, on the basis that it is practically impossible to determine
a) which compounds could be classed as drugs and
b) which transporters could function as drug transporters.
Users looking for this role should find everything and use their judgment to narrow down based on the substrate specificity of interest.

In #15379 we mentioned merging into the parent; would that be OK for you @cmungall @ValWood ?

GO:0015238 drug transmembrane transporter activity -> GO:0022857 transmembrane transporter activity
GO:0015893 drug transport -> transport (I'll try to make this TM transport if annotations are consistent)
GO:0006855 drug transmembrane transport ->

@pgaudet:

In 15379 we mentioned merging into the parent,

My response is in my original comment above:

If we agree to obsolete then we should decide if it is (a) a merge or (b) obsolete + replace/consider. I would strongly favor the latter, as I think we want to have clear information for people who do search on this and other drug concepts (e.g. "this terms was obsoleted because ... you may want to consider ..."). I think non-exact synonyms to the alternate terms may be justified.

And val said:

Definitely obsolete and reannotation

I thought the plan was to remove the CheBI 'role' of drug, which would get rid of all children, and people could annotate to 'drug transmembrane transporter' with a CHEBI term if they want to.
For example these terms would not be under 'drug transporter activity':

GO:1901235 (R)-carnitine transmembrane transporter activity
GO:1903089 5-amino-1-ribofuranosylimidazole-4-carboxamide transmembrane transporter activity
GO:0005277 acetylcholine transmembrane transporter activity

Thanks, Pascale

I thought the plan was to remove the CheBI 'role' of drug

yes, the plan is to never axiomatize using this ChEBI class, and to examine all GO classes that reference this class, likely obsoleting them. This ticket is about drug transmembrane transporter

which would get rid of all children

not sure what you mean exactly

and people could annotate to 'drug transmembrane transporter' with a CHEBI term if they want to

the proposal is to obsolete 'drug transmembrane transporter'

For example these terms would not be under 'drug transporter activity':

Correct, because it would be obsolete

Some annotations that would need to be rehoused if we obsoleted

GO:0015238 | drug transmembrane transporter activity
GO:0015893 | drug   transport
GO:0006855 | drug transmembrane transport
GO:0046618 | drug   export
GO:0061772 | drug transport across blood-nerve barrier
GO:1990962 | drug transport across blood-brain barrier
GO:1905699 regulation of drug transmembrane export
GO:1905700 negative regulation of drug transmembrane export
GO:1905701 positive regulation of drug transmembrane export

https://docs.google.com/spreadsheets/d/1hynVdp5Gh93lXxDa-pJx0qyDEH59IeW8ADY4njiuhmo/edit#gid=0
It's 227 annotations by the following groups:
Contributor   (Assigned by) | Number of annotations
AspGD | 4
CGD | 67
EcoCyc | 33
EcoliWiki | 3
Ensembl | 1
GeneDB | 14
GOC | 4
MGI | 1
MTBBASE | 1
PomBase | 1
PseudoCAP | 23
RGD | 26
SGD | 31
TAIR | 3
UniProt | 14
UniProtKB | 1

Most impacted groups are
CGD
EcoCyc @keseler
Pseudocap @glwinsor
RGD @slaulederkind
SGD @srengel
UniProt @milarolo

Hi @pgaudet what are the suggested replacement terms?  that is, rehouse these annotations how?

The proposal is to rehouse the annotations directly to the substrate being transported.

Any term with a logical definition that refers to a 'role', we would remove that logical definition.

"The proposal is to rehouse the annotations directly to the substrate being transported."
Many of the E. coli proteins annotated to drug transmembrane transport or drug transmembrane transporter activity are efflux pumps with multiple substrates. Does that create a problem for the proposal is to rehouse the annotations directly to the substrate being transported?"
EcoCyc@keseler

An alternative proposal (that I think @ukemi also supports) would be to simply remove all children from the 'drug' terms, stop inferring what compounds are drugs, and encourage co-annotation to the substrate AND to drug transport when appropriate.
Any preference ? (and why?)
Thanks, Pascale

Leaving the term sounds a sensible solution. We just can't define what constitutes a drug. My main concern is that at present all of our amino acid transporters, and others are inferred as drug transporters due to chebi role. I would be happy if this was fixed.

I could commit an intermediate version that looks like this

As opposed to the current version:

(and doing the same on the BP terms above).
The remaining classes are asserted, we can decide what to do with them in a second step, but I think they are 'real' drugs.
Does that sound like a reasonable first step @ukemi @cmungall @ValWood @srengel @dsiegele ?

The alternative proposal isn't mine. It's the one the consortium agreed upon many years ago. I suspect there are some children of the drug terms that are not chemicals, but are drug roles. For example, in your list above, drug:proton antiporter activity. I notice we also have antibiotic terms. We should spec out how the co-annotation would look in a GO-CAM model.

The alternative definitely looks better than the current.

For example, in your list above, drug:proton antiporter activity. I notice we also have antibiotic terms.
All classes that I kept in this version are asserted. We should look one by one which ones to remove (I would personally do this as a separate ticket to avoid too many changes at once).

GO-CAM model with two classes for an activity:
http://noctua.geneontology.org/editor/graph/gomodel:5c4605cc00002220

My original proposal was to obsolete this altogether. My proposal was not to universally replace it with the substrate (although that is fine in some situations), but to replace it with a term that reflects what the function of the gene product is.
Regarding @dsiegele's question, see my analysis at the top of the ticket, in this case I believe your replacement term would be:
id: GO:0015562
name: efflux transmembrane transporter activity
def: "Enables the transfer of a specific substance or related group of substances from the inside of the cell to the outside of the cell across a membrane." [GOC:ai, GOC:mtg_transport, ISBN:0815340729]
synonym: "efflux permease activity" EXACT []
synonym: "monocarboxylate (lactate, pyruvate, mevalonate) uptake/efflux porter activity" RELATED []
is_a: GO:0022857 ! transmembrane transporter activity

If people prefer to simply have a hardcoded list of chemicals that are considered drugs and for us to take on the burden of maintaining this, we can do this but we will need to allocate more resources, and it seems unsatisfactory.

Sorry, didn't mean to confuse multiple issues-- I wasn't commenting on the drug transporter term, I was just trying to show how to co-annotate two terms to the same activity.  Look at http://noctua.geneontology.org/editor/graph/gomodel:5c4605cc00002220 again.
I agree with Chris that we need to consider the (evolved) function.  I also favor removing "drug" from the terms.  If we want to specify an evolved function, in many cases it would be appropriate to use the more general "xenobiotic "(with drug as a narrow/inexact synonym for searching) to describe a class of molecules of exogenous origin.  So curators could annotate to "xenobiotic transporter activity", for instance.  Xenobiotic will of course be defined relative to the species of the gene product being annotated, which we would not try to encode in any way but leave up to curators.

Yes, I think many existing annotations would be better served by an annotation to xenobiotic TM transport plus a separate indication of the compound if known

Backtracking, I agree. It would be more consistent
For xenobiotics should the compound always be specified as a CHEBI extension?
If so, could we remove terms like
GO:0015240    amiloride transmembrane transporter activity (0 annotations)
GO:0015350 methotrexate transmembrane transporter activity (6 annotations)
to encourage consistency and best practice?

I agree with the obsoletion.

Decisions ontology call:

[x] Merge 'drug transmembrane transporter' into 'xenobiotic transmembrane transporter'
[ ] Merge 'drug transmembrane transport' into 'xenobiotic transmembrane transport'

SWIE done

Hi,
I've only had time to skim this thread quickly. I've noticed that GO:0015893 'drug transport' has lots of children that I wouldn't necessarily expect, e.g. 'oxygen transport'. So I searched the issue tracker for GO:0015893. Is the work that you plan to carry out for this ticket going to fix/modify that situation? :-) Thanks!
Paola

Hi @paolaroncaglia
Reasoning over CHEBI roles ticket will fix this:
https://github.com/geneontology/go-ontology/issues/14626

I thought that stopping reasoning over CHEBI roles was implemented  recently? but I still have 39 random  inferred transporter annotations to "drug transport".

It hasn't been implemented yet. We are still discussing what the full resolution should be once we stop reasoning over roles. It is a big task.

Naive question: will this merge risk reviving the problem caused by roles when a molecule (like some estrogens) is both a normally occurring metabolite and a drug? Now will they be seen as xenobiotics because xenobiotic transporters mediate their movement?

Yes I don't know why I thought it was done.

I'm not sure that the problem here is entirely due to reasoning over roles.
I have "drug transporter" annotations for things like
L-methionine
uracil
pyridoxal
uridine
succinate....
are there really classified as drugs by CHEBI?

I don't see this:
https://www.ebi.ac.uk/chebi/searchId.do?chebiId=CHEBI:30031
under roles

succinate doesn't appear to be related to "drug" at all.
https://www.ebi.ac.uk/chebi/chebiOntology.do?chebiId=CHEBI:26806
odd...

Yes, the things on your list really do all have paths to "drug" or "drug metabolite" in CHEBI. Not all of the paths are entirely has_role+is_a; for example, for succinate it includes traversing a couple of "is conjugate base of" links to reach succinic acid.

AH OK, I could not see 'drug'  in the CHEBI  graph I looked at. So isn't it just a case of ignoring some relationships . Am I being naive?

I think there's probably also something to do with the way GO lumps some CHEBI terms so we don't have to worry too much about the conjugate acid/conjugate base business. If so, then yeah, one consequence is that it's not easy to see enough of the CHEBI paths at once to understand where all of the "drug" inferences are coming from.

We cannot resolve all 'roles' here but we can avoid using the term 'drug', which we have agreed multiple times to do.
To do to close this ticket:

[ ] merge GO:0015893  drug transport into GO:0042908 xenobiotic transport
(annotations have been reviewed in https://github.com/geneontology/go-annotation/issues/2332
[ ] merge GO:0046618 drug export into GO:0140330 xenobiotic detoxification by transmembrane export across the cell outer membrane (see https://github.com/geneontology/go-annotation/issues/2334)
[ ] GO:0006855 drug transmembrane transport merge into GO:0042908 xenobiotic transport
[ ]  GO:0042908 xenobiotic transport : change label to 'xenobiotic transmembrane transport'

Thanks, Pascale

Perhaps worth noting that 'xenobiotic' and 'drug' are both ChEBI roles and not completely overlapping. Depending on how we decide to deal with ChEBI roles, it might not make sense to merge drug into xenobiotic. I do agree that we should stop coding specific compounds as 'drugs' in the ontology, but the same flaw might also apply to 'xenobiotic'.

Sure, but 'xenobiotic' is more general than drug. It's just a band aid but it would be good to remove all instances of 'drug' in the ontology.

'xenobiotic' is more general

But perhaps not general enough. To me penicillin and colchicine are xenobiotics, but to the fungus and plant that make them?

Sure, but 'xenobiotic' is more general than drug. It's just a band aid but it would be good to remove all instances of 'drug' in the ontology.

I agree that what we are currently doing with 'drug' is a problem, but the more I look at ChEBI roles, I am starting to think that merging 'drug' terms into 'xenobiotic' terms will just be keeping the problem with a different name.

Sure - the point was that all annotations to the dugs terms have been reviewed, so we reduce the number of terms we need to deal with later on.
It would be good if no new annotations were made to drug terms, and the only way I see is to merge with a term we at least plan to keep.
Up to you, of course.
Thanks, Pascale

As discussed in the ticket: handling terms for xenobiotic role and removing drug role #19460, we have decided on these actions. For more detail about specific terms, go the the ticket linked above.

MF terms ("drug binding" & 2 xenobiotic transporter activity terms) - will be made OBSOLETE as it doesn't make sense to describe a molecular function based on the context a chemical is being used in. Annotations will need to be reviewed and transferred to an appropriate MF term based on chemical specificity if possible.
BP terms (transport terms, metabolic terms, response terms) - "drug" terms will be merged into the corresponding "xenobiotic" terms if one exists, or renamed from "drug" to "xenobiotic" if not.
regulation BP terms - There only a few of these all variations of "regulation of response to drug", so we will request for these to be reviewed and then decide if they should be converted to "xenobiotic" terms or Obsoleted.

As the new ticket comprehensively covers the plan for all of the drug and xenobiotic terms, I'm going to close this ticket.

authors: ValWood cmungall deustp01 dsiegele krchristie mah11 milarolo paolaroncaglia pgaudet srengel thomaspd ukemi


text:
GO:0031508   pericentric heterochromatin formation

single inheritance
GO:0031508   pericentric heterochromatin formation
has only one none-regulation child
GO:0140727   siRNA-dependent pericentric heterochromatin formation
are there other mechanisms of pericentromeric heterochromatin assembly, or do they all involve siRNA-dependent
@colinlog
(for pombe it is only siRNA-dependent)

There are non.RNA dependent mechanisms of pericentric heterochromatin formation, see for eg PMID:14612388
So we decided to

[ ] remove parent ''small ncRNA-mediated heterochromatin formation'' from 'pericentric heterochromatin formation' ''
[ ] add direct asserted superclass ''small ncRNA-mediated heterochromatin formation' to GO:0140727 siRNA-dependent pericentric heterochromatin formation

Are you sure about this?

There are non.RNA dependent mechanisms of pericentric heterochromatin formation, see for eg PMID:14612388

"These results are consistent with a model in which Lsh is recruited by intact heterochromatin structure and then assists in maintaining heterochromatin organization by establishing CpG methylation patterns."
I remember when we  originall discussed  this, we concluded that establishment (aka formation) was always via siRNA mechanisms.
this paper (PMID:14612388) is describing  non-RNA dependent mechanisms for maintaining pericentric heterochromatin, (i.e after it is formed). Do you have any other papers supporting a non RNAi-based mechanism for pericentromeric heterochromatin formation?

We obsoleted 'heterochromatin maintenance' - the paper states "These results are consistent with a model in which Lsh is recruited by intact heterochromatin structure and then assists in maintaining heterochromatin organization by establishing CpG methylation patterns" - so heterochromatin formation still seems OK for this.
Do you suggest hat we restore heterochromatin maintenance ? Then would that be RNA-independent?

Actually, if
[RNAi-dependent heterochromatin assembly.]stays under
pericentric heterochromatin formation
this is probably OK.

source: gharchive/issue

authors: ValWood pgaudet

repo: geneontology/go-ontology

license_type: permissive

license_source: github-api


text:
NTR: multi-eIF complex

Hi,
I'd like to request a term for a multifactor translation initiation
complex. Based on the paper listed below, it could be called "multi-eIF
complex". Another, longer, option might be "multifactor translation
Initiation factor (eIF) complex", and the one not used for the term name
could be the synonym.
A possible def would be:
A multifactor complex composed of multiple translation initiation
factors and the initiatior tRNAiMet, which is ready to bind to the small
(40S) ribosome to form the 43S preintiation complex. In S. cerevisiae,
this complex is composed of eIF1, eIF2, eIF3, and eIF5.
Here are some relevant quotes from the paper and the citation and
pubmed ID are below.
thanks,
-Karen
In cerevisiae, the (eukaryotic) translation Initation Factors (eIF's) eIF1,
eIF2, eIF3, and eIF5 form a multifactor complex free of 40S ribosomes.
The multi-eIF complex is associated with initiator tRNAiMet in vivo
The ability of eIF1, eIF3, eIF5, and the ternary complex to associate
independently of the 40S ribosome raises the possibility that these
factors bind to the 40S ribosome as a preformed unit. This could
facilitate rapid assembly of 43S preinitiation complexes containing
these factors, requiring only the addition of eIF1A and the mRNA/
eIF4F/PAB1 complex to produce a 48S complex capable of locating the
AUG start codon and hydrolyzing the GTP bound to eIF2.
Asano K, Clayton J, Shalev A, Hinnebusch AG (2000) A multifactor
complex of eukaryotic initiation factors, eIF1, eIF2, eIF3, eIF5, and
initiator tRNA(Met) is an important translation initiation intermediate in
vivo. Genes Dev 14(19):2534-46
PubMed ID: 11018020
Reported by: krchristie
Original Ticket: "geneontology/ontology-requests/3110":https://sourceforge.net/p/geneontology/ontology-requests/3110

thanks www.movied.org


text:
1.10.0 RC

Major Release

This release brings cf-genesis-kit up to date with the releases found in
cf-deployment v12.25.0.

New Features

Log Throttling: by specifying params.max_log_lines_per_second, you can
limit the maximum log lines per second per app instance.  A value of 0
disables this limit (which is the default state).
Note: This is an EXPERIMENTAL feature, and as such, should not be used in
a production environment without full understanding of its implications.
See the associated Pivotal Tracker story

Core Components

Release
Version
Release Date

bpm
1.1.6
05 December 2019

capi
1.89.0
06 December 2019

cf-networking
2.27.0
02 December 2019

cf-smoke-tests
40.0.125
03 January 2020

cflinuxfs3
0.154.0
14 January 2020

cf-cli
1.24.0
08 January 2020

diego
2.42.0
14 January 2020

garden-runc
1.19.9
21 November 2019

loggregator
106.3.5
13 January 2020

loggregator-agent
5.3.4
13 January 2020

log-cache
2.6.8
30 December 2019

nats
32
11 December 2019

routing
0.196.0
05 December 2019

statsd-injector
1.11.13
13 January 2020

cf-syslog-drain
10.2.9
13 January 2020

uaa
74.13.0
13 January 2020

silk
2.27.0
02 December 2019

bosh-dns-aliases
0.0.3
24 October 2018

cflinuxfs2
1.286.0
12 June 2019

app-autoscaler
2.0.0
15 August 2019

nfs-volume
2.3.0
21 August 2019

mapfs
1.2.0
15 July 2019

postgres
3.2.0
19 September 2019

haproxy
9.7.1
05 September 2019

Buildpacks

Release
Version
Release Date

binary
1.0.36
08 January 2020

dotnet-core
2.3.3
08 January 2020

go
1.9.4
08 January 2020

java
4.26
21 November 2019

nginx
1.1.3
08 January 2020

nodejs
1.7.8
08 January 2020

php
4.4.5
08 January 2020

python
1.7.5
08 January 2020

r
1.1.1
08 January 2020

ruby
1.8.6
08 January 2020

staticfile
1.5.3
08 January 2020

Note: Core Component and Buildpack releases in italics were updated as part of this kit release.

Version bumps and log rate-limiting addition
LGTM

source: gharchive/pull-request

authors: dennisjbell krutten

repo: genesis-community/cf-genesis-kit

license: MIT


text:
Feat: create common method of api client with authentication header

Overview

Create common method of api client with authentication header

Changes

Added common HTTP client method with authentication header
Change file structure of backend api client atdata.ts
Replace axios with fetch API

Note

After this PR is merged, please try to use request method in commonUtils.ts to call HTTP request to RESTful backend API

Out of scope (Future work)

#156
#74

Assignee Checklist:

[x] The base branch is correct (See: Types of Branches)
[x] The branch name follows the Branch Naming Conventions
[x] The correct assignees and reviewers have been designated for this PR
[x] The coding style follows the Coding Style Guide
[x] All the related issues are associated with this PR
[x] All criteria in the associated issues are met (please tick the checkboxes)
[x] My changes do not generate new warnings or errors (especially in the console)

Reviewer Checklist:

[x] The code follows the generic best practices and our Coding Style Guide
[x] Code is well-commented and easy to understand
[x] UI changes accurately reflect the provided design

Thank you for your review guys!

repo: genesis-tech-tribe/nishiki-frontend


text:
Consolidate steps that are repeatedly used together

See the comment on PR #431 and investigate the pattern in that workflow and others for possible refactoring

We have a this tool for VCFs now - subworkflows/bgzip_and_index.cwl  Would be good for someone to take a quick pass through and see if there's anywhere it should be subbed in.

authors: chrisamiller johnegarza

repo: genome/analysis-workflows


text:
Fix linting warning

Fixes
WARN: A process with name 'MODKIT_PILEUP_HAPLOTYPES' is defined more than once in module script: /home/runner/work/nallo/nallo/./workflows/../subworkflows/local/methylation.nf -- Make sure to not define the same function as process

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

LGTM! There are no outputs in the subworkflow, but I am guessing that is correct

For another time 😄

repo: genomic-medicine-sweden/nallo


text:
Test the profiler Kaiju

Kaiju finds maximum (in-)exact matches on the protein-level using the Burrows–Wheeler transform.
TO DO
Compare the Kaiju classification to Kraken2 (genome-level) based on clinical case #374764.

Kaiju database: Protein sequences from genome assemblies of Archaea and bacteria with assembly level "Complete Genome", as well as viral protein sequences from NCBI RefSeq.
Kraken2 database includes archaea, bacteria, viral, human, UniVec_Core, protozoa and fungi.
Inference:
For a DNA sample:
There were 1017 reads assigned to Viruses, a significantly larger number compared to Kraken2, which had only 33 reads assigned to Viruses. This disparity aligns with the observations made in Kaiju's original paper. However, I suspect one of key factors contributing to this difference is that the Kaiju database lacks human genome sequences, which typically constitute a substantial portion—up to 99%—of the total classified reads. Furthermore, many predicted virus reads were identified as human reads by BLAST.
This finding is consistent with the Kaiju original paper's assertion that Kaiju can classify up to 10 times more reads in actual metagenomic scenarios. But it also has higher false positives than Kraken2 in our case.
Update:
To address these discrepancies, it is wise to prepare Kaiju DB by including human, fungi, and plasmid sequences to re-perform the comparisons.

repo: genomic-medicine-sweden/taxprofiler


text:
Improve unit test coverage for ServiceIOGroup and BatchServer

estimate 2

The ServiceIOGroup and BatchServer have some negative test cases missing, and so there is not good coverage of exception management.
Done criteria:

[x] Pull request that improves coverage is merged
[x] Test cases are added that cover exceptions

Pull request #2007 was merged into dev.

repo: geopm/geopm


text:
Update PlatformTopo C++ man page

Man page of PlatformTopo refers to geopm::PlatformTopo::domain_cpus(...), which is not a method of the class any more.
using geopm::PlatformTopo;

int main() {
    PlatformTopo &topo = geopm::platform_topo();
...
    for (int pkg_idx = 0; pkg_idx < num_pkgs; ++pkg_idx) {
        std::cout << "CPUs on package " << pkg_idx << ": ";
        std::set<int> cpus = topo.domain_cpus(GEOPM_DOMAIN_PACKAGE, pkg_idx);
        for(auto pcpu : cpus) {
            std::cout << pcpu << " ";
        }
        std::cout << std::endl;
    }

Also geopm::platform_topo() return type is now  const.
#454

Thank for the feedback @vysocky!  The domain_cpus() became private and was replaced by the more general domain_nested() method.  I will update the documentation to reflect this change soon.

https://review.gerrithub.io/c/geopm/geopm/+/455130

authors: cmcantalupo vysocky


text:
Implement dynamic status response and data response

Description
Currently, PyWPS uses static files for status response (e.g. http://localhost:5000/outputs/51eb13f2-7ea9-11e8-be8f-08002710f680.xml)
This works fine, as long there is no Exception stored in the file (status=True). If the client downloads the file, response code will always be 200. But we should implement correct status code returning.
Same applies for stored files: It should be implemented as service (e.g. https://apps.sentinel-hub.com/eo-browser/ uses WMS for data retrieving), since the data can no longer be only files, but e.g. stored in database.

Hello,
I implement a draft of dynamic status. I'm not very happy with my draft but at less it's work. I will need it to handle process queue.
https://github.com/gschwind/PyWPS/commit/014951ec295a737b0f17eb23d3d625a14e0441f0
Best regards

authors: gschwind jachym

repo: geopython/pywps

license: mit

license_source: bigquery


text:
GEXF Legend

Discuss legend specification: https://github.com/gephi/gexf/tree/legend/specs/1.3.1

Great start! One minor comment to start the conversation :)

In viz:color maybe for is better than use so it's similar to attavalue, when we refer to a column

The use attribute disappeared after we chose to nest viz-colors into the corresponding attribute.
I propose we move the discussion in the PR page.

authors: mbastian paulgirard

repo: gephi/gexf


text:
🛑 Hacker News is down

In a68dce8, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hacker News is back up in 0183023 after 5 minutes.

repo: gerrited/upptime


text:
🛑 k3s WeatherForecast is down

In 47896b0, k3s WeatherForecast (https://k3s.g11s.cc/WeatherForecast) was down:

HTTP code: 0
Response time: 0 ms

Resolved: k3s WeatherForecast is back up in ad927e0.


text:
chore: only pass svc to NewAPI

Doesn't make sense to pass svc and also pass svc.AlbyOAuthSvc, and especially when svc.AlbyOAuthSvc is only being used twice in NewAPI methods

I was trying to remove reliance on the service, which in order to do so actually we need to move things into packages. But I guess this is ok to merge for now

authors: im-adithya rolznz

repo: getAlby/nostr-wallet-connect-next


text:
Complete implementation of v2 CardSet

Complete implementation of v2 CardSet (requires small modification to AST structure)
++
====

--

~~

====
++

Released in https://github.com/getMoreBrain/bitmark-parser-generator/releases/tag/v1.0.4

repo: getMoreBrain/bitmark-parser-generator

license: ISC


text:
Guru Claim Request: ZIO

Gurubase Username:
Milad Khajavi
khajavi@gmail.com
Guru Link:
https://gurubase.io/g/zio
Proof of Maintainership:
https://github.com/zio/zio/graphs/contributors

[!Note]
We would love to see multi-account maintainership support

I’ve assigned it to your Gurubase account. You can find it on the 'My Gurus' page.
I'll update this thread once multi-account maintainership support is available. In the meantime, can you provide the other maintainers' Gurubase usernames?

Whenever it is available, I can provide the usernames.
Question: Is there any way to change the visibility settings of the PDFs we uploaded to the knowledge base?
We would like to prevent the sharing of these PDFs. For the PDF I’ve uploaded, Zionomicon, we want users to access the book only by submitting a form on the zionomicon.com website to request a copy.

That makes sense. Currently, there isn’t a way to do that. I’ll think about it and update this thread.

authors: khajavi kursataktas

repo: getanteon/gurubase


text:
Use AppMap Gradle plugin to attach the agent

Based on https://github.com/getappmap/appmap-intellij-plugin/pull/367, which needs to be merged first
Tests are currently broken because of https://github.com/getappmap/appmap-gradle-plugin/issues/18

Closing, upstream has not been fixed yet and we have a working solution atm.

repo: getappmap/appmap-intellij-plugin


text:
Customizable accent color

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Selectable color palette allowing to pick favorite color.
Describe alternatives you've considered
Leave as it is.
Additional context
Accent color, purple-ish, is clearly related to logo color.
I would be perfect to be able to pick color of choice.

I just pushed 942466e which implements this feature, it should be shipped with the next Beta build.
The accent color can now be changed inside Settings > Accent color.

Available in v5.4.0-beta.1.

authors: kytwb pawelantczak vantezzen

repo: getferdi/ferdi


text:
Gauge.captureScreenshot() ignores user specified ClassInstanceManager

We run each scenario in its own Spring context, therefore we have unique ClassInitializer(based on Spring ApplicationContext) and unique instance of CustomScreenshot for each scenario. Current Gauge.captureScreenshot() implementation  has single ClassInstanceManager instance across all scenarios
Expected behavior
I should be able to take screenshots via Gauge.captureScreenshot() when if I have unique CustomScreenshot per scenario
Actual behavior
Gauge.captureScreenshot() uses wrong CustomScreenshot instances due to incorrect ClassInitializer. Screenshots are taken for wrong scenario
Steps to reproduce

Set unique ClassInitializer BeforeScenario using ClassInstanceManager.setClassInitializer()
Run tests in parallel
Check screenshots

@ZhyliaievD Could you please provide a very basic sample project which I can use to replicate this issue? I'm afraid I do not have good knowledge about spring, so it would a bit difficult and time-consuming to replicate this.

authors: BugDiver Korop ZhyliaievD

repo: getgauge/gauge-java


text:
Show Diagnostics LSP

Gauge LSP server should support publish diagnostics for spec and concept files.
The server should publish diagnostics when the document changes.
This story is part of LSP support for gauge.
Test cases

[x] Should show critical errors
[x] Should show spec parse errors
[x] Should show concept parse errors
[ ] Should show unimplemented steps
[ ] duplicate step definition

Currently diagnostics for error Should show unimplemented steps  and  duplicate step definition is shown only for Javascript.
Fix should be available with following nightlies =>
gauge      => 09-1-2017
gauge-js => 09-1-2017

Issues

[ ] Unimplemented step is not getting highlighted
[ ] Duplicate step implementation is not being shown
[ ] Number of usages are also not displayed

test1.zip

Please reopen the spec file or edit the spec file for the errors to get highlighted, because diagnostics load when there a file change or when you open the file.

Closing this issue as the unimplemented step is working as designed.
Unable to replicate the duplicate step issue consistently.

Getting diagnostics on wrong lines
Getting step implementation not found on the wrong line

test1.zip

Getting step implementation not found on existing valid steps.

Getting a duplicate step implementation on a step that is not implemented

test1 (2).zip

Getting a duplicate concept defined even if one of the folders is configured in gauge_exclude_dirs

Change in way diagnostics are published
All files are validated and diagnostics are published for all files.
Diagnostics are published when

when gauge lsp server is initialized
a gauge file(.spec and .cpt) is opened
any file is changed (gauge or implementation files)

Available in gauge nightly >= 20/11/17.
please check if commit hash b306205

Switching between a js file and spec file gives step not implemented error.
Steps to replicate

Checkout project LSP tests
Open diagnostics.js
Open autocomplete.spec

Observe the errors on all steps

Steps with duplicate step implementation does not show the error
Steps to replicate

Project - test1 (2).zip
Open in VSCode

Observe there are duplicate step implementations for all steps.
However no error is displayed on the spec files

The duplicate step implementations do not go away when a file with the duplicate steps are deleted.
Steps to replicate

Project - test1 (2).zip
Open in VSCode
Delete the new_test.js
Close all files
Open the spec file

Observe there are duplicate step implementations are still there.

Duplicate concept definitions are not indicated
Steps to replicate

Project - test1 (2).zip
Open in VSCode
The concept named Concept has duplicate definitions.
Open the concept files one.cpt and newConcept.cpt.

Observe they do not indicate the duplicate Concept definitions.

Expected behavior
Concept Circular reference should be shown in a both usages.
Actual behavior
Circular reference is shown only on one usage
Steps to replicate

Create concepts with circular reference

# Concept1
* Concept2

# Concept2
* Concept1

Expected behavior
Deletion of a code file should update the step definitions accordingly
Actual behavior
Getting an existing connection forcibly closed

Steps to replicate

On a new project
Copy paste step_implementation.js into the same project
Close all files
Select step_implementation.js file. Delete it permanently
Open example.spec file

Observe red lines indicating that existing connection was forcibly closed

Fix should be available in gauge and gauge-js nightly >= 22/11/17

authors: Apoorva-GA BugDiver nehashri sguptatw

repo: getgauge/gauge


text:
Recommendation: Theme template standards

In the Grav documentation, it says:

There are no set rules regarding the structure of a Grav theme except that there must be appropriate Twig templates provided in the templates/ folder for each of the page types you use in your content.

I would recommend changing that to the benefit of the end user. I ran into this when trying to change themes was that pages that were attached to templates that didn't have the same name/path in another theme, it caused an instant exception.
Because there are no set rules for a Grav theme, there is inherent incompatibility between themes built into Grav. In other words, Grav is currently designed for themes to fail, which isn't a great user experience and could be improved.
What I would recommend instead:

Establish a few very simple and limited rules for "base" templates required for a theme.
Publish a set of recommended guidelines for template structuring including paths and names.
Set a behavior in Grav that missing templates will fallback to particular default templates. (Set in No. 1)

What do you think?

I'm not sure what "rules" you'd create. Depending on the content you're trying to serve, you may only need one or two templates. I guess it wouldn't be too burdensome to say all themes must have a "default" template. I'm just not sure what you gain.

Immediately following the quote you pulled you'll also see the following:

A good way to create general themes is to support the template types used by the Skeleton packages that are available on our downloads page. For example, support: default, blog, error, item, and modular.

What additional guidance might you suggest? I agree that documentation is really important. If you use the Devtools plugin to create the theme, you can see that it does create some basics for you. That might be a good place to make changes, too.

Fallback sounds nice, but what would it fall back to? Let's say we mandated a "default" template but one didn't exist, should Grav use something built in? Even if some built-in fallback were created, I would rather know that something was wrong (via exception) than get unintended output. A missing template is indeed a problem to be solved.

I agree that to compete with CMSs like WordPress, theme changing needs to be as painless as possible. I'm just not sure how far the core system can go to mitigate this.
(I'm not a team member, just an avid user.)

Even if there wasn't a clear fallback, if Grav wants to keep it's flexibility, then there should be a way to users to either cast (overwrite and change) pages to the new theme's templates, or alias (map to a theme's templates, but without changing the values in case you want to switch back).
Right now, it just breaks, and after failing to figure out where it was breaking, or figuring out an easy way to just try out the theme without a bunch of tedium, I just kind of threw up my hands and went back to the original theme.
As far as additional guidance, the part about "a good way" is good, but I would switch that to recommended, along with a list of optional recommended theme file names.
Another problem, I noticed (I think) that not only does the filename have to match, but they have to be in the same folder structure, no? I could be wrong about that.
Anyway, I think you get what I'm saying. Right now page migration between themes is very painful, and it really doesn't have to be. And because it's so painful, I think it's even a bit misleading to call them "themes", because I would say that there's a user expectation that they behave like Wordpress themes i.e. they are (mostly) interchangeable. They behave more like libraries that have a unique API.

There is no folder structure involved. When Grav goes to the requested folder, it looks for an X.md file. It then looks in the user/themes/THEME/templates folder for X.html.twig and applies it, regardless of where exactly X.md lives.
As for modifying existing themes, there is a best practice for that. It's a simple matter to symlink templates to a new name so you don't have to change your existing page data. But this does indeed require facility with the terminal. I don't use the Admin plugin, so I have no direct experience with this, but I know they are working hard to make it easy for non-command-line folks to do this sort of thing with relative ease. It's not an easy thing, though.

Just to add my two-cents, even just having a list of suggested core theme Twig template filenames would be helpful - I think in some ways Antimatter has served this purpose for blog sites. For non-blog sites is there a suggested list of template files/names?
One thing I've started to do in my own custom themes is to also provide a default Twig file for modular content, just to help get things going 🙂

This is by design. A theme has much more power than what other popular CMS grant to themes.
That's part of Grav's flexibility, a theme is not just a skin. The theme is a fundamental part of the design of the site, not just the UI but the information architecture, the functionality etc.
That's why you can't really switch themes easily, unless the themes are very general / simple.
This is what allows Grav sites to be very different with minimal use of plugins. Consider the skeletons RTFM, Receptar, Ceevee, Course Hub, they can do what they do because the theme has special handling for special page types.
This is no different than what happens with other CMS as well, considering for example Custom Post Types in WP.
Then, it's nice if every theme could provide a default page, and a blog structure for example, but it's not required.

I think this has been answered already, but for clarification:

Grav is not a typical CMS where the theme is purely a skin over your site.  The theme is an integral part, and as Grav has no real requirements as to how you structure your site, not can the theme.

This is by design.  Grav is built this way to ensure it's supremely flexible, and can be tailored to support any kind of site design you wish.  I believe this is one of the reasons why it's so hard to work with WordPress/Joomla/etc as they enforce strict rules on what a theme can do, what it provides, etc. Grav has no such limitations and is better for it.

Grav makes it pretty easy to create 'skeleton' packages which are really ready-to-roll demo sites with content + configuration + plugin + theme.  This means that you can create wildly different site types and make them easy to install and modify by the end user.  This is not typically a simple thing for other platforms.

I would suggest theme designers grab a theme they wish to use as their basis, and follow the structure/templates of that theme for their own.  Antimatter is the closest thing Grav has for a kitchen-sink type theme, that can handle a single page design (via modular twig templates), blog layout, and simple pages.  That is a good model to copy if you wish to provide a more 'general' theme.

authors: Perlkonig flaviocopes matthew-dean paulhibbitts rhukster

repo: getgrav/grav


text:
Infinite recursion error with moto 5.0.8

After upgrading our CI container from moto 5.0.7 to 5.0.8 we started seeing an infinite recursion error in one of our test cases.
Ran 1 test in 2.552s

FAILED (errors=1)
/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/auth.py:419: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
  datetime_now = datetime.datetime.utcnow()

Error
Traceback (most recent call last):
  File "/home/aws/test/test_vpc.py", line 240, in test_create_vpc_flow_logs_in_account_moto
    vpc_func.create_vpc_flow_logs_in_account(self.ctx_obj, dst_bucket='test-bucket')
  File "/home/aws/vpc_func.py", line 108, in create_vpc_flow_logs_in_account
    completed_future.result()
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/aws/vpc_func.py", line 40, in create_flow_log
    response = client.create_flow_logs(
               ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/client.py", line 565, in _api_call
    return self._make_api_call(operation_name, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/client.py", line 1001, in _make_api_call
    http, parsed_response = self._make_request(
                            ^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/client.py", line 1027, in _make_request
    return self._endpoint.make_request(operation_model, request_dict)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/endpoint.py", line 119, in make_request
    return self._send_request(request_dict, operation_model)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/endpoint.py", line 202, in _send_request
    while self._needs_retry(
          ^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/endpoint.py", line 354, in _needs_retry
    responses = self._event_emitter.emit(
                ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/hooks.py", line 412, in emit
    return self._emitter.emit(aliased_event_name, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/hooks.py", line 256, in emit
    return self._emit(event_name, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/hooks.py", line 239, in _emit
    response = handler(**kwargs)
               ^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/retryhandler.py", line 207, in __call__
    if self._checker(**checker_kwargs):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/retryhandler.py", line 284, in __call__
    should_retry = self._should_retry(
                   ^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/retryhandler.py", line 307, in _should_retry
    return self._checker(
           ^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/retryhandler.py", line 363, in __call__
    checker_response = checker(
                       ^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/retryhandler.py", line 247, in __call__
    return self._check_caught_exception(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/retryhandler.py", line 416, in _check_caught_exception
    raise caught_exception
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/endpoint.py", line 278, in _do_get_response
    responses = self._event_emitter.emit(event_name, request=request)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/hooks.py", line 412, in emit
    return self._emitter.emit(aliased_event_name, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/hooks.py", line 256, in emit
    return self._emit(event_name, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/botocore/hooks.py", line 239, in _emit
    response = handler(**kwargs)
               ^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/core/botocore_stubber.py", line 37, in __call__
    response = self.process_request(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/core/botocore_stubber.py", line 84, in process_request
    status, headers, body = method_to_execute(
                            ^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/core/responses.py", line 290, in dispatch
    return cls()._dispatch(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/core/responses.py", line 501, in _dispatch
    return self.call_action()
           ^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/core/responses.py", line 587, in call_action
    response = method()
               ^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/ec2/responses/flow_logs.py", line 23, in create_flow_logs
    flow_logs, errors = self.ec2_backend.create_flow_logs(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/ec2/models/flow_logs.py", line 231, in create_flow_logs
    s3_backends[self.account_id][self.partition].get_bucket(arn)  # type: ignore[attr-defined]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/s3/models.py", line 1848, in get_bucket
    return s3_backends[account_id][self.partition].get_bucket(bucket_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/s3/models.py", line 1848, in get_bucket
    return s3_backends[account_id][self.partition].get_bucket(bucket_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/s3/models.py", line 1848, in get_bucket
    return s3_backends[account_id][self.partition].get_bucket(bucket_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  [Previous line repeated 970 more times]
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/s3/models.py", line 1845, in get_bucket
    if not s3_allow_crossdomain_access():
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/.pyenv/versions/3.12.3/lib/python3.12/site-packages/moto/settings.py", line 76, in s3_allow_crossdomain_access
    return os.environ.get("MOTO_S3_ALLOW_CROSSACCOUNT_ACCESS", "true").lower() == "true"
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen _collections_abc>", line 807, in get
  File "<frozen os>", line 682, in __getitem__
RecursionError: maximum recursion depth exceeded

I looked at the code under test, which is in a private repositories so I cannot share all the details publicly here.
Something different about that code is that it is called under:
 with concurrent.futures.ThreadPoolExecutor(max_workers=max_workers) as executor:

Then the infinite recursion happens when we call:
        for completed_future in concurrent.futures.as_completed(futures):
            completed_future.result()

The boto3 code call was create_flow_logs() for EC2.

Hi @sodul, thanks for raising this. I've just pushed a fix for this - are you able to reproduce it with moto >= 5.0.9.dev8?

Tested:

5.0.7: works
5.0.8: fails with the infinite recursion
5.0.9.dev8: works

Thanks for the quick fix!

Great, thanks for confirming that @sodul.
I've just released 5.0.9, so I'll close this then.

authors: bblommers sodul

repo: getmoto/moto


text:
Add beforeScreenshotCallback to SentryFlutterOptions

:scroll: Description

Add beforeScreenshotCallback to SentryFlutterOptions

:bulb: Motivation and Context

Closes #1540
:green_heart: How did you test it?

Unit tests

:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[ ] No new PII added or SDK only sends newly added PII if sendDefaultPii is enabled
[ ] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

Was looking for this, thanks!  When it will be released ?

@Juliocsreis hey we'll do a release this week :)

@Juliocsreis this release should be out on 7.15.0

@Juliocsreis this feature is now included in 7.15.0

Thank you very much 😄

authors: Juliocsreis buenaflor denrase

repo: getsentry/sentry-dart


text:
Any new releases planned?

I had to switch from the latest release to the GitHub upstream, does there happen to be any releases planned in the near future or should I keep my dependency pointed to the repo?

@Zelzahn absolutely, we're working on releasing 8.1.0. 🙃 Should be out in the next few days.

authors: Zelzahn whatyouhide

repo: getsentry/sentry-elixir


text:
Streamline and align the "Getting Started" docs to fit in the new structure

Problem Statement

The "Getting Started" documentation for sentry-php platforms may not conform to the newly defined format, which includes the steps "Install", "Configure", "Verify", and the optional "Next Steps".

The "Verify" step is not always available and it is a very important step that helps the user to verify that the installation and configuration were done correctly.

New users onboarding with Sentry may find the existing documentation extensive and unclear. The "Getting Started" guide should cover the basics, while more advanced configurations shall live on the sentry-docs website.
Some copies and code snippets in the documentation may be outdated.

Solution Brainstorm
The task goals are as follows:

Thoroughly review all sentry-php platform documentation, including less commonly used sections, and reorganize their content into structured headings: 'Install,' 'Configure,' 'Verify,' and the optional 'Next Steps.'
The onboarding documentation should strictly focus on the basics to help users get started. Advanced configurations should be available in the complete documentation on the sentry-docs website.
Essential information for new users should be included under the new 'Notes' section in the onboarding documentation.
Update code snippets and copies as necessary.
If a "Verify" step is missing, include it in the documentation.

Please refer to the "Frontendend Handbook" guide in our "Sentry" main repository for assistance in adding and updating the getting started docs: Frontendend Handbook.
Project: https://github.com/getsentry/team-sdks/issues/23

https://github.com/getsentry/sentry/pull/55843#event-10308151727

authors: cleptric priscilawebdev

repo: getsentry/sentry-php


text:
Add M8 Additional Resources Notebook for P1

Hi @apvoges
It seems the Additional Resources notebook was removed. Could we add this back for M8 of P1?
Thanks,
Dean

Not to worry @apvoges!
Just spotted that M8 should already be populated. I'll take this through Asana to update instructions.
Thanks,
Dean

repo: getsmarter/bda


text:
Error loading shared library libsqlite3.so.0: No such file or directory (needed by /usr/local/bin/bitcoind)

Upon losing a carrier and immediately before acquiring a new carrier, the following errors occur.
umbrel dhcpcd[700]: veth32bd5b5: removing interface
umbrel dhcpcd[700]: veth3be4691: carrier lost
umbrel bitcoin[729]: Error loading shared library libsqlite3.so.0: No such file or directory (needed by /usr/local/bin/bitcoind)
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_column_text: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_close: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_column_int: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_reset: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_clear_bindings: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_open_v2: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_column_bytes: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_shutdown: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_exec: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_config: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_backup_step: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_db_readonly: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_backup_init: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_finalize: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_get_autocommit: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_step: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_backup_finish: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_errstr: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_errmsg: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_column_blob: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_initialize: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_libversion: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_prepare_v2: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_bind_blob: symbol not found
umbrel bitcoin[729]: Error relocating /usr/local/bin/bitcoind: sqlite3_open: symbol not found
umbrel dhcpcd[700]: veth3be4691: carrier acquired

I suspect this is due to libsqlite3 i386 missing, and can be fixed by adding
sudo apt install libsqlite3-0:i386
or merely libsqlite3-0:i386 to the appropriate list of packages.
I am not sure which one that is, hence an issue instead of a PR.
If is already being installed, there are issues and a sudo apt install --reinstall libsqlite3-0:i386 should do the trick.

i386

That would be the version for Intel 32 bit computers, and not for arm64 RPis.
Also, this needs to be present inside one container, not on the host. This bug is already reported, we'll provide a fix soon.

i386

That would be the version for Intel 32 bit computers, and not for arm64 RPis.
Also, this needs to be present inside one container, not on the host. This bug is already reported, we'll provide a fix soon.

Of course, my bad.
Sounds good with the fix.

repo: getumbrel/umbrel-os


text:
Calling HighchartsChartObject.redraw function doesn't work.

Hi Guys
In my case I'm using Angular2. When I try to change the chart.type of my chart ('line', 'column',etc) it doesn't work.
Is it necessary to do something else than calling the redraw or is a problem?.
Thanks in advance,
J

I think it is more question about Highcharts rather than angular2-highcharts. Look at this example http://jsfiddle.net/5wzm6ncu/.

You are right. Thanks.

authors: JBreto gevgeny


text:
Segmentation fault on Metal when creating pipelines from multiple threads

Short info header:

GFX version: master
OS: OSX
GPU: Intel 630

Can be reproduced with high chance on VK CTS test: "api.object_management.multithreaded_per_thread_device.graphics_pipeline".
Call stacks are different, often in set_fragment_function, sometimes in newRenderPipelineStateWithDescriptor.
This looks like a memory corruption issue, possibly because of our misuse of Metal, some internal issue in SPIRV-Cross, or something else. Needs to be investigated!

Note: Assuming you got CTS built, running a single test under lldb can be done with:
make cts name=api.object_management.multithreaded_per_thread_device.graphics_pipeline

repo: gfx-rs/gfx


text:
🛑 GFX Productions™ API is down

In e1cc9bb, GFX Productions™ API (https://api.gfx-pro.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GFX Productions™ API is back up in 14a1f6e.

repo: gfxpronet/upptime


text:
Gist support

I love the work! I notice that, trying to use a Gist (https://gist.github.com/alexwhittemore/fb5913c8146ab441e795a13f9ec8d7ea) rather than a commit in a proper repo, I get no output (the frame renders, but no notebook). Digging into nbconvert.php, it looks like you're parsing the URL methodically to extract info about the repo, user, and so on in order to make sure you're always pulling the latest version of the file. It seems to me like that would architecturally preclude the plugin working for Gists?
Additionally, on that Gist page, I see a pretty handy looking "embed" option. It ends up creating a scrolling iframe, which I don't much love, but it's certainly easy and pretty. I suppose another disadvantage vs nbconvert is that it's not auto-updating.
So perhaps for my use-case (I don't want to serve out of a proper repo), either this embedded gist scheme, or raw HTML manually exported from Jupyter Notebook might be more appropriate solutions?

Hey, literally all that needs to happen is to point any link to nbviewer... So there was no need for me to start breaking up the url anyways! I will fix this when I get around to it. Other than that, pull requests welcome!

authors: alexwhittemore ghandic

repo: ghandic/nbconvert


text:
Add graphics/qgis-ltr and graphics/qgis  to GhostBSD binary packages for installation to GhostBSD.  Already exists in FreeBSD

Describe the feature or enhancement
Please place QGIS & QGIS-LTR into GhostBSD supported binary packages
QGIS is at 3.28.7 version number
QGIS-LTR is at 3.22 version number
Why this request?
S P uses QGIS software in his daily work and wishes to use QGIS on his home GhostBSD computer
also development manager view  URL link is not working  https://github.com/orgs/ghostbsd/projects/4/views/12
FreeBSD Pkgs 13  QGIS pkg
FreeBSD Ports QGIS for 13.1
FreeBSD directory browser for QGIS port

PDAL did not compile.
/wrkdirs/usr/ports/math/pdal/work/PDAL-2.3.0-src/pdal/Geometry.cpp:143:26: error: cannot initialize a variable of type 'OGRSpatialReference *' with an rvalue of type 'const OGRSpatialReference *'
    OGRSpatialReference *srs = m_geom->getSpatialReference();
                         ^     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/wrkdirs/usr/ports/math/pdal/work/PDAL-2.3.0-src/pdal/Geometry.cpp:162:26: error: cannot initialize a variable of type 'OGRSpatialReference *' with an rvalue of type 'const OGRSpatialReference *'
    OGRSpatialReference *inSrs = m_geom->getSpatialReference();
                         ^       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I completely forgot to close this issue since it is available.
> pkg search qgis-ltr
qgis-ltr-3.28.9_1              Free and Open Source Geographic Information System

repo: ghostbsd/issues


text:
Update docs generators to include proper edit on github links

Ref: https://github.com/ghostty-org/website/pull/197
The "Edit on Github" links currently on ghostty.org link to the downstream MDX files. This has lead to multiple folks editing the downstream MDX files.
Preview:
https://website-git-edit-on-github-link-override-ghostty.vercel.app/docs/config/reference#auto-update-channel

Well this is fancy as hell. Nice!

I'm gonna merge in https://github.com/ghostty-org/website/pull/197 so we have the functionality.  This will just need to get in before the next regeneration.

authors: BrandonRomano mitchellh

repo: ghostty-org/ghostty


text:
Enforce team name

Add team ownership

Thanks @whites11 I was going to take care today :)

repo: giantswarm/crsync


text:
create_release_pr: Handle First Release

Problem
The create_releae_pr workflows fail in new projects without any pre-existing release, if automatic release numbering is attempted.
Thus it is not possible to simply create a first release v0.0.1, v0.1.0 or v1.0.0 using the documented release#major#minor#patch branch name interface.
This is how the workflow without this PR fails if no previous release exists:

Solution
Handle the gh api repos/$1/releases/latest failing and assume version 0.0.0 if the error message contains Not Found.
See this screenshot for illustration:

Was discovered during creation of https://github.com/giantswarm/personio-go for giantswarm/giantswarm#24049

repo: giantswarm/devctl


text:
Add MimirRulerTooManyFailedQueries

Towards: https://github.com/giantswarm/giantswarm/issues/32042
Adding a new rule to detect failure in Mimir ruler evaluation

Here is how this alert would have been triggered on various installations over the last 30 days
alba

wallaby

gazelle

armadillo

Can you put it under the correct rule group? It's.under Mimir.continuous-test

authors: QuentinBisson TheoBrigitte

repo: giantswarm/prometheus-rules


text:
GS OS Decision

Task
Decide which operating system is supported by Giant Swarm with CAPI.
TODOs:
- [ ] Evaluate current options
- [ ] Make decision based on the current information
- [ ] Comunicate the decision (Slack, SAs, etc.)
- [ ] Publish ADR

Background
The operating system of choice for Giant Swarm has been Flatcar until now because:

container support used to required a recent kernel. There were bugs fixed, new features added, different storage drivers, etc.
the OS was focused on container support, streamlined, etc. Other operating systems had a lot of bloat (package manager, unneeded packages installed by default);
the OS hardening rules are already implemented. Another OS requires additional work to implement and to valuate with customers.

Some customers started asking for security agents (e.g. MS Defender) to run directly on supported operating system and to have full access to the system (internal security requirements). In the case of MS Defender, Flatcar is not one of the supported operating systems even if both are owned by Microsoft (see Microsoft's documentation).
Flatcar has very few users with CAPI. We will be among the few to run the Ignition bootstrap code from upstream. This increases the risk of encountering problems which need to be fixed without much help from upstream.
Most upstream clusters are probably running Ubuntu (it's the default). Nowadays the operating system is less important for running containers. Most features are available on most Linux distributions and there aren't cutting edge features required by the workloads or the container runtime.
Current status

AWS & Azure Vintage are using Flatcar;
CAPA is using Flatcar;
CAPZ is using Flatcar;
CAPV is using Ubuntu, but it has upstream support for Flatcar (not yet tested by Giant Swarm: Slack thread);
CAPVCD is using Ubuntu, and Giant Swarm is adding Flatcar support upstream (https://github.com/giantswarm/roadmap/issues/2506);

Options
Flatcar
GS only uses Flatcar as the operating system.
Pros

container native OS. Higher risk that we need to deal with issues on our own;
hardening already implemented;
security validated by existing customers;
GS has experience with it;
most GS CAPI providers are already using it: CAPA, CAPZ, CAPV, CAPVCD (in progress);
has an LTS version (but we haven't tried it yet);

Cons

very few actual users;
secondary OS in CAPI. GS would not benefit from all the testing done by upstream;
not yet supported for some GS CAPI providers: CAPG (on-hold), CAPVCD (in progress);
the LTS version wasn't easy to use when we tried (probably, because we weren't building our own images);
higher risk that we need to deal with issues on our own;
Microsoft? What's the future of Flatcar?

Ubuntu
GS only uses Ubuntu as the operating system.
Pros

main OS used by CAPI upstream. GS would benefit from all the testing done by upstream;
very popular OS. There's a lot of information on the Internet (issues, fixes, workarounds, etc.);
LTS release with 5 years of support (customers can get a support contract from Canonical);
GS would be aligned with upstream;

Cons

general purpose OS, not container native. It's less important nowadays;
GS has less experience with it;
the OS hardening needs to be implemented;
the OS needs to be validated by our customers;

Both (Flatcar & Ubuntu)
GS mainly uses Flatcar as the operating system and keeps the option available to use Ubuntu for customers with additional requirements which can't be met by Flatcar.
Pros

larger customer base;

Cons

maintenance overhead. Supporting 2 operating systems requires additional effort especially if they are configured in a different way (ignition vs cloud-init);

Other OS
GS switches to a different Linux distribution (not Flatcar or Ubuntu).
Pros
None without considering a specific distribution.
Cons

migration effort: build new images, update OS configuration, etc.

@Rotfuks I finished adding all the context about the OS decision.
Personally, I'm in favor of sticking with Flatcar for now mostly because:

the cloud provider are already using it (CAPA, CAPZ);
we don't have a current customer with a special request;
we don't need to redo the security validation of the OS with our customers (it's already approved by existing customers);
CAPV has upstream support;
CAPVCD work is in progress;
we build our own images and we can add agents to the os (if needed). We already did it for Teleport;

Then let's document it as decision to stick to Flatcar as the target state.
I think it's a decision fitting to our previous concept decisions in the providers that we just formalize here. So I'll add it to the Turtles decision log and we can close it with that outcome :)

PR for decision log: giantswarm/giantswarm#27997

authors: Rotfuks alex-dabija

repo: giantswarm/roadmap


text:
Sql view params

Howdy howdy and happy Friday
I needed expanded functionality for specifying parameters in published SQL View layers, so I have implemented it into the publish_featurestore_sqlview method.
Specific things to note:

New optional parameter parameters, which is an iterable of dicts with names that correspond (snake_case to camelCase) to the necessary XML entries used by Geoserver to define the parameters for SQL Views (docs)
Totally reworked TestFeatures to account for these changes, and made it automatically build up the necessary database and geoserver content, and tearing it down at the end.
To the above point, I also expanded the stuff in tests/common.py to allow you to specify a database in which to run tests. Maybe some of the current "local only" tests can be refactored to use this as well.
Two new dev dependencies were introduced, I hope that that isn't a problem. They are sqlalchemy and psycopg2, used to work with the database when setting up & tearing down the database during testing.

Let me know what you think, I can tweak this further

😱 I completely missed this PR!
https://github.com/gicait/geoserver-rest/pull/144
Sorry about that..

repo: gicait/geoserver-rest


text:
improve service scope to prevent memory leak in case scope not being …

…despoce

Ops, we will need to change the implication.
We need to send to ninject some kind of context.
A Bind to a Scope
C is Transient contains A
The problem grain is resolving factory of c and create multiple objects from this factory
expected behavior A will be a singleton for this scope

repo: gigya/microdot


text:
Hovers over Iframes are broken

When I hover over Iframe trying to use this plugin there is an error:
Uncaught TypeError: Cannot read property 'x' of undefined
    at HTMLDivElement.getValues (tilt.jquery.js:91)
    at HTMLDivElement.updateTransforms (tilt.jquery.js:106)
getValues @ tilt.jquery.js:91
updateTransforms @ tilt.jquery.js:106

It works perfectly with everything else, but not with one thing I need. I wanted to apply this effect to google maps iframe.
I guess this is kind of issue so here I am :)

Hey, thanks for reporting. Can you provide a codepen example so i can see the issue?

@gijsroge Here is an example: https://jsfiddle.net/orpavLep/
If you hover over iframe it doesn't work, but it works on everything else.

I don't think it's just iframes, I also get it but i'm not sure on what currently
the error appears to be in
https://github.com/gijsroge/tilt.js/blob/a92d1bda917e1ba0d0981a6d5cf539917e3cc13b/src/tilt.jquery.js#L119
const percentageX = (this.mousePositions.x - left) / width;
thanks
J

@gijsroge
I temporarily added this line to the top of  getValues
if(!this.mousePositions) this.mousePositions = getMousePositions.call(this);
that theoretically would get rid of the error cannot read property 'x' of undefined
however it suggests something is getting called in the wrong order or not being instantiated in time
thanks
j

Thank you so much you saved my life!!!

authors: Levelleor Rawquete gijsroge jmp909


text:
hailo-tappas-core_3.28.1_arm64.deb file does not exist.

Where can I download the hailo-tappas-core_3.28.1_arm64.deb file?

Hi thank you for your interest. This is still on development.
It will be released soon in hailo's official website. Then you will be able to run it.


text:
Changelog to new Freatures

Atualmente, a tradução está sendo feita a partir da versão v0.3.76 (versão padrão na Steam):
 Forum Terra Invicta
A tarefa atual é apenas traduzir sem revisar esta versão :large_blue_circle:. Após a conclusão, teremos dois problemas para manter a sincronização.
1° Precisamos comparar o arquivo da versão default anterior com a nova
Nesse processo via software, vamos levantar os arquivos ou textos adicionados, removidos e alterados
2° Remover e Adicionar as chaves na tradução
Nessa etapa, vamos modificar dos items detectados na etapa anterior.
Com isso, deve ser possivel evitar dor de cabeça.

Programa para comparar as versões:
https://gist.github.com/gilberto-009199/13b117c0d85ea127286c8724e849f08f
Exemplo de output:
  Define 1st source directory:
	 esp_0.3.76
     (y)es or (n)ot }> y
  Define 2st source directory:
	 esp_0.3.76
     (y)es or (n)ot }> n
	 esp_0.3.77
     (y)es or (n)ot }> y
Summary:
	 * TIArmyTemplate.esp
	    keys: 484
	 * TIBatteryTemplate.esp
	    keys: 22
	 * TICinematicsTemplate.esp
	    keys: 90
	 * TICondition.esp
	    keys: 117
	 * TICouncilorTemplate.esp
	    keys: 12
	 * TICouncilorTypeTemplate.esp
	    keys: 48
	 * TICouncilorVoiceTemplate.esp
	    keys: 15
	 * TIDriveTemplate.esp
	    keys: 627
	 * TIEffectTemplate.esp
	    keys: 685
	 * TIFactionIdeologyTemplate.esp
	    keys: 26
	 * TIFactionTemplate.esp
	    keys: 242
	 * TIFormationTemplate.esp
	    keys: 65
	 * TIGunTemplate.esp
	    keys: 20
	 * TIHabModuleTemplate.esp
	    keys: 292
	 * TIHabSiteTemplate.esp
	    keys: 507
	 * TIHabTemplate.esp
	    keys: 16
	 * TIHeatSinkTemplate.esp
	    keys: 29
	 * TILaserWeaponTemplate.esp
	    keys: 203
	 * TILocalizationTemplate.esp
	    keys: 17
	 * TIMagneticGunTemplate.esp
	    keys: 96
	 * TIMetaTemplate.esp
	    keys: 24
	 * TIMiningProfileTemplate.esp
	    keys: 54
	 * TIMissileTemplate.esp
	    keys: 61
	 * TIMissionTemplate.esp
	    keys: 437
	 * TINarrativeEventTemplate.esp
	    keys: 2326
	 * TINationTemplate.esp
	    keys: 915
	 * TINavigableTemplate.esp
	    keys: 117
	 * TIObjectiveTemplate.esp
	    keys: 1023
	 * TIOperationTemplate.esp
	    keys: 119
	 * TIOrbitTemplate.esp
	    keys: 765
	 * TIOrgTemplate.esp
	    keys: 275
	 * TIParticleWeaponTemplate.esp
	    keys: 33
	 * TIPlasmaWeaponTemplate.esp
	    keys: 32
	 * TIPolicyTemplate.esp
	    keys: 75
	 * TIPowerPlantTemplate.esp
	    keys: 148
	 * TIPriorityPresetTemplate.esp
	    keys: 43
	 * TIProjectTemplate.esp
	    keys: 1485
	 * TIRadiatorTemplate.esp
	    keys: 28
	 * TIRegionTemplate.esp
	    keys: 1198
	 * TIResourceCost.esp
	    keys: 5
	 * TIShipArmorTemplate.esp
	    keys: 28
	 * TIShipCommandTemplate.esp
	    keys: 108
	 * TIShipHullTemplate.esp
	    keys: 42
	 * TISpaceBodyTemplate.esp
	    keys: 2118
	 * TITechTemplate.esp
	    keys: 499
	 * TITraitTemplate.esp
	    keys: 222
	 * TIUtilityModuleTemplate.esp
	    keys: 85
	 * TIVictoryTemplate.esp
	    keys: 22
	 * UIArmy.esp
	    keys: 13
	 * UICodex.esp
	    keys: 257
	 * UICouncil.esp
	    keys: 16
	 * UICouncilor.esp
	    keys: 191
	 * UICouncilorChat.esp
	    keys: 41
	 * UIFleets.esp
	    keys: 284
	 * UIGeneralControls.esp
	    keys: 120
	 * UIGlobal.esp
	    keys: 75
	 * UIHabs.esp
	    keys: 154
	 * UIIntel.esp
	    keys: 92
	 * UIMarkers.esp
	    keys: 15
	 * UIMissionPhase.esp
	    keys: 19
	 * UINation.esp
	    keys: 414
	 * UINations.esp
	    keys: 46
	 * UINotifications.esp
	    keys: 635
	 * UIObjectives.esp
	    keys: 608
	 * UIOperations.esp
	    keys: 51
	 * UIOptions.esp
	    keys: 186
	 * UIScience.esp
	    keys: 107
	 * UISpace.esp
	    keys: 57
	 * UISpaceCombat.esp
	    keys: 116
	 * UIStartScreen.esp
	    keys: 181
	    [ DIFF ] UI.StartScreen.SolarSystem
  Files adding/remove:
	 * /home/administrador/Desktop/terra invicta tradução/esp_0.3.77/teerw.esp

Assim podemos saber os arquivos e chaves adcionadas/alterar/removidas entre as versões. Seria bom se possivel criar um workflow no github para alterar automaticamente o Status.

Versão Inicial para download:
v0.3.76.zip

Nova versão na Steam:
v0.3.99.zip

Programa para comparar as versões:
https://gist.github.com/gilberto-009199/13b117c0d85ea127286c8724e849f08f
Exemplo de output:
  Define 1st source directory:
	 Scanner
     (y)es or (n)ot }> n
	 esp_v0.3.76
     (y)es or (n)ot }> y
  Define 2st source directory:
	 Scanner
     (y)es or (n)ot }> n
	 esp_v0.3.76
     (y)es or (n)ot }> n
	 esp_v0.3.99
     (y)es or (n)ot }> y
  Summary:
	 * TIArmyTemplate.esp
	    keys: 484
	 * TIBatteryTemplate.esp
	    keys: 22
	 * TICinematicsTemplate.esp
	    keys: 90
	 * TICondition.esp
	    keys: 117
	 * TICouncilorTemplate.esp
	    keys: 12
	 * TICouncilorTypeTemplate.esp
	    keys: 48
	 * TICouncilorVoiceTemplate.esp
	    keys: 15
	 * TIDriveTemplate.esp
	    keys: 627
	 * TIEffectTemplate.esp
	    keys: 685
	 * TIFactionIdeologyTemplate.esp
	    keys: 26
	 * TIFactionTemplate.esp
	    keys: 242
	 * TIFormationTemplate.esp
	    keys: 65
	 * TIGunTemplate.esp
	    keys: 20
	 * TIHabModuleTemplate.esp
	    keys: 292
	 * TIHabSiteTemplate.esp
	    keys: 507
	 * TIHabTemplate.esp
	    keys: 16
	 * TIHeatSinkTemplate.esp
	    keys: 29
	 * TILaserWeaponTemplate.esp
	    keys: 203
	 * TILocalizationTemplate.esp
	    keys: 17
	 * TIMagneticGunTemplate.esp
	    keys: 96
	 * TIMetaTemplate.esp
	    keys: 24
	 * TIMiningProfileTemplate.esp
	    keys: 54
	 * TIMissileTemplate.esp
	    keys: 61
	 * TIMissionTemplate.esp
	    keys: 437
	 * TINarrativeEventTemplate.esp
	    keys: 2326
	 * TINationTemplate.esp
	    keys: 915
	 * TINavigableTemplate.esp
	    keys: 117
	 * TIObjectiveTemplate.esp
	    keys: 1023
	 * TIOperationTemplate.esp
	    keys: 119
	 * TIOrbitTemplate.esp
	    keys: 765
	 * TIOrgTemplate.esp
	    keys: 275
	 * TIParticleWeaponTemplate.esp
	    keys: 33
	 * TIPlasmaWeaponTemplate.esp
	    keys: 32
	 * TIPolicyTemplate.esp
	    keys: 75
	 * TIPowerPlantTemplate.esp
	    keys: 148
	 * TIPriorityPresetTemplate.esp
	    keys: 43
	 * TIProjectTemplate.esp
	    keys: 1485
	 * TIRadiatorTemplate.esp
	    keys: 28
	 * TIRegionTemplate.esp
	    keys: 1198
	 * TIResourceCost.esp
	    keys: 5
	 * TIShipArmorTemplate.esp
	    keys: 28
	 * TIShipCommandTemplate.esp
	    keys: 108
	 * TIShipHullTemplate.esp
	    keys: 42
	 * TISpaceBodyTemplate.esp
	    keys: 2118
	 * TITechTemplate.esp
	    keys: 499
	 * TITraitTemplate.esp
	    keys: 222
	 * TIUtilityModuleTemplate.esp
	    keys: 85
	 * TIVictoryTemplate.esp
	    keys: 22
	 * UIArmy.esp
	    keys: 13
	 * UICodex.esp
	    keys: 257
	 * UICouncil.esp
	    keys: 16
	 * UICouncilor.esp
	    keys: 191
	 * UICouncilorChat.esp
	    keys: 41
	 * UIFleets.esp
	    keys: 284
	 * UIGeneralControls.esp
	    keys: 120
	 * UIGlobal.esp
	    keys: 75
	 * UIHabs.esp
	    keys: 154
	 * UIIntel.esp
	    keys: 92
	 * UIMarkers.esp
	    keys: 15
	 * UIMissionPhase.esp
	    keys: 19
	 * UINation.esp
	    keys: 414
	 * UINations.esp
	    keys: 46
	 * UINotifications.esp
	    keys: 635
	 * UIObjectives.esp
	    keys: 608
	 * UIOperations.esp
	    keys: 51
	 * UIOptions.esp
	    keys: 186
	 * UIScience.esp
	    keys: 107
	 * UISpace.esp
	    keys: 57
	 * UISpaceCombat.esp
	    keys: 116
	 * UIStartScreen.esp
	    keys: 181

Nenhuma alteração entre arquivos!

license: Unlicense


text:
Include html files to pod source target

This PR is related to https://github.com/gilesvangruisen/Swift-YouTube-Player/issues/24, but does not solve problem completely yet.
Hi, thank you for a great library.
I realised YouTubePlayer.podspec 's source_files does not contain html.
So I fixed it and it works as expected, but still get unexpectedly found nil while unwrapping an Optional value fatal error.
I use CocoaPods with a Podfile below:
# Podfile
platform :ios, '8.0'
use_frameworks!

pod 'YouTubePlayer', :git => 'https://github.com/ymkjp/Swift-YouTube-Player', :branch => 'feature/20150913_fix_podspec'

Thanks.

Sorry for the late response. Thanks for this!

authors: gilesvangruisen ymkjp

repo: gilesvangruisen/Swift-YouTube-Player


text:
Handle DW_AT_MIPS_linkage_name and DW_AT_specification

Also some noise from running newer rustfmt.
Fixes #35

Coverage remained the same at 0.0% when pulling 5eb142e95f30e2ef76e6bc8c092da6d0c5f743be on philipc:issue-35 into 5de3429ee0dbcf5389b5e246b490e93c53ea879a on gimli-rs:master.

Perhaps we should do a new point release as well?

@philipc Nice!
@fitzgen Yeah, that seems reasonable.

authors: coveralls fitzgen jonhoo philipc


text:
Motor stops running runBackard/runForward after executing forceStopAndNewPosition

Hi gin66,
Using executing runBackward() method a few times the motor stops running and does not respond to runBackward().
To explain our code:
We have a while loop and a timer for 30seconds.
Every time I enter a command to Start the motor, the motor will runBackward() for 30seconds and then stop (forceStopAndNewPosition) and wait for the next command again.
I will enter "Start" command again and the motor will run for 30seconds again and stop.
The problem is that after I "Start" the motor after the 2nd or 3rd time the motor will not run.
The timer is still running as expected and other parts of code are working as expected.
runBackward or runForward do not respond after 2nd/3rd time calling the method.

On further testing and reviewing other #33  it seems that the issue has to do with forceStopAndNewPosition(0).
I updated the code to use stopMove() instead and I was able to run "Start" multiple times without any issues.
There is definitely some issue with forceStopAndNewPosition().
I'm using version 0.18.10.
I've updated the title to reflect this.

On further testing and reviewing other #33  it seems that the issue has to do with forceStopAndNewPosition(0).
I updated the code to use stopMove() instead and I was able to run "Start" multiple times without any issues.
There is definitely some issue with forceStopAndNewPosition().
I'm using version 0.18.10.
I've updated the title to reflect this.

Looks like a duplicate to #33.
In the test_seq_09.cpp I constantly start the motor with runForward()/runBackward() followed by forceStopAndNewPosition(). But I have never observed, that it does no respond to a new run...ward() command. Nevertheless I hope, that the fix for #33 let this problem disappear, too.

Looks like a duplicate to #33.
In the test_seq_09.cpp I constantly start the motor with runForward()/runBackward() followed by forceStopAndNewPosition(). But I have never observed, that it does no respond to a new run...ward() command. Nevertheless I hope, that the fix for #33 let this problem disappear, too.


text:
Does not compile in ESPhome

Hi, thanks for transferring this to ESPhome. Unfortunately it does not compile in my ESPhome V 1.19.4. I tried with ESP8266 Wemos D1 mini. The Error report:
In file included from src/main.cpp:17:0:
src/mhi_ac_ctrl.h: In member function 'virtual void MhiAcCtrl::control(const esphome::climate::ClimateCall&)':
src/mhi_ac_ctrl.h:323:35: error: switch quantity not an integer
switch (this->fan_mode) {
Do you have an idea whats the problem?
Thank you very much!
Johannes

Hi, @ACMHI thank you for reporting!
I've just pushed a commit that might fix it (I'm far away from my A/C, so can't test atm), please check!
Looks like in the latest ESPHome they've made "fan_mode" an "optional", so it was missing a single asterisk.

Hi ginkage,
cool, thanks, now it compiles without issues :-)

Confirmed to be fixed.

authors: ACMHI ginkage

repo: ginkage/MHI-AC-Ctrl-ESPHome


text:
Histogram range editor

Resolves #1117, resolves #1109, resolves #1122
Histograms include a mode to "exclude distribution tails". When this mode is enabled, the inputs for min and max become percentages from the ends. These automatically chop off 1% from each end (but if a bucket includes more than 1%, it may end up as more - in the below example, the minimum excludes 2%). The user can still change these values.

Histograms are drawn with some logic to shorten the height of the max frequency if it eclipses all other values.
From @manthey via Slack:

let v0 be the highest value in the histogram and v1 be the second highest.  Make the top of the histogram min(v0, v1 * 1.5), so that the second highest value is 2/3 the total height unless making it so would make the highest value less than the total height.

An example without max frequency shortening:

The same histograms drawn with max frequency shortening:

I see a lot of extraneous parameters in the tile style queries (layerName, custom, defaultMin, etc).
Also, it doesn't seem to switch to the composited image until I fiddle with a setting -- I was expecting the previous behavior where all of the channels are composited without any specified min/max values until some value has been specified.  This means that the range we display should probably be based purely on the dtype until we fiddle with values.
I don't seem to be able to type fractional percentages in the scale range (I type 0.2 and immediately it reverts to 0).

Eventually (in another PR), it'd be nice to be able to specify a default for any channel that has blank min/max values.  That is, by default all channels would start with blank min/max values.  If the overall defaults are set to 0.2% / 0.2% or 100 / 20000, then any channel with blank values would use those values, but channels with specified values would use those specific values.  Clearing the numerical values in a channel would go back to using the default, and clearing the default would mean min / max are unspecified in the style.

Can we make the default auto-range be 0.2% (not 0.02%) and prevent the user from dragging it past 50%?

I removed the vue-switches dependency in d5b27c4 and now the tests are passing :+1:

When I clear the entry in the min or max edit fields, I see a console error: Error: <text> attribute x: Expected length, "NaN".

When I try to show all the histograms of a many channel image, it is asking for the wrong frame for the histogram.  Rather than asking for frames 0,1,2,3,4,... it is asking for 0,1,3,6,10,...  My guess is that frame and framedelta are both set.

When I clear the entry in the min or max edit fields, I see a console error: Error:  attribute x: Expected length, "NaN".

Fixed in 4a46617

When I try to show all the histograms of a many channel image, it is asking for the wrong frame for the histogram. Rather than asking for frames 0,1,2,3,4,... it is asking for 0,1,3,6,10,... My guess is that frame and framedelta are both set.

Fixed in 448ef26

When you have scrolled down the list of channels, the color picker is out of view (scrolling up shows it).

When you have scrolled down the list of channels, the color picker is out of view (scrolling up shows it).

Changed in 3e2fd3a. Rather than having a color picker component for every row in the table with each being relative to the color picker column, we now have one color picker component relative to the table header, which is sticky during scrolling.

authors: annehaley manthey


text:
Fix an issue searching for annotation metadata

If a user has permission to view an annotation but not the item, a 403 was percolated to the UI

To replicate, create an item in a public folder with an annotation with metadata that you can find in a search.  Switch the folder to private.  The annotation metadata search throws a 403 that is visible in the UI.  After this change, the item just isn't listed.


text:
Improve testimonial section

Is your feature request related to a problem? Please describe.
I would like to bring the testimonial to the center of the page
Describe the solution you'd like
add justify-content property in CSS file
Describe alternatives you've considered
NA
Additional context
NA
Original

Modified

@codewithvk I am a GSSOC'21 participant. Please assign me this issue.

@Sapna2001 Go Ahead!

repo: girlscript/Girscript-Community-Website


text:
Android-Kotlin : 09.9 Navigation Drawer with Fragment in Android (Kotlin)

Description 📜

Give a step-by-step tutorial of Navigation Drawer with Fragment in Android (Kotlin).
Required Documentation or Video or Audio.

Domain of Contribution 📊

[x] Android Dev (Flutter, Java, Kotlin)

References :

https://www.simplifiedcoding.net/android-navigation-drawer-example-using-fragments/

Please Read it Carefully Before Contributing

Changes should be made in Android_Development_With_Kotlin/ directory under Android_Development_With_Kotlin branch.
Inside Android_Development_With_Kotlin/ directory creates a directory and names it according to the topic ( for this issue 09. Dynamic User Interface)
Inside 09. Dynamic User Interface/ directory add your task with subtopic number and name and make changes accordingly.
You have to push your PR to the Android_Development_With_Kotlin branch only.
You can take help to the references but don't simply try to copy it. Just explain in your own word.
This issue is for GWOC'21 contributors only.
You need to push in a single commit. If there exists more than one commit then you need to squash your commits into one commit.
Will assign you on a first come first serve basis.
Please try to complete your assigned task within 7 days. If you need some more time then, please inform mentors and supervisors.
If you have two previously assigned issues on Android-Kotlin pending then please first complete them.

Supervisor @rahulsain

Happy Contributing. Best of Luck.💖

/assign

Hey @rahulsain and @sitamadex11 I have created the PR, You can have a look now, and is there are no issues you can merge it.
THANKYOU

repo: girlscript/winter-of-contributing


text:
Android Kotlin: 09.30  How to use SearchView on ToolBar?

Description :scroll:

Give a step-by-step tutorial on How to use SearchView on ToolBar.
Required Documentation or Video or Audio.

Domain of Contribution :bar_chart:

[x] Android Dev (Kotlin)

References :
https://www.javatpoint.com/android-searchview-on-toolbar

Please Read it Carefully Before Contributing

Changes should be made in Android_Development_With_Kotlin/ directory under Android_Development_With_Kotlin branch.
Inside Android_Development_With_Kotlin/ directory creates a directory and names it according to the topic ( for this issue 09. Dynamic User Interface)
Inside 09. Dynamic User Interface/ directory add your task with subtopic number and name and make changes accordingly.
You have to push your PR to the Android_Development_With_Kotlin branch only.
You can take help to the references but don't simply try to copy it. Just explain in your own word.
This issue is for GWOC'21 contributors only.
You need to push in a single commit. If there exists more than one commit then you need to squash your commits into one commit.
Will assign you on a first come first serve basis.
Please try to complete your assigned task within 7 days. If you need some more time then, please inform mentors and supervisors.
If you have two previously assigned issues on Android-Kotlin pending then please first complete them.

Supervisor @rahulsain

Happy Contributing. Best of Luck.:sparkling_heart:

/assign


text:
Hooks in React.js

Description
what is hooks
How to Import Hooks in React.js
Rules of Hooks
Example
Domain
Frontend Dev React/Angular/Vue
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


text:
Java Switch Blocks

Description 📜
Explained Switch Blocks in Java
Fixes #1808

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Java_Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@AkMo3 please review my work

@ShikhaSwati60 Will be review by @sakshamlamba109 first. @sakshamlamba109 Please complete the review and let me know

Add References, if any, it will be a good practice.

@sumitaccess007 My bad, please complete the review

/assign documentation

Yes, it's good.

@AkMo3 Do I need to add anything else in my file or is it ready to get merged?


text:
Data Science with Python : Hand Made Graphs Visualization using Cutecharts Library (#4162)

Description 📜
I did extensive documentation and prepared a jupyter notebook on Hand Made Graphs Visualization using Cutecharts Library, and how it's applied using sample code. Added one README.md MD and one IPYNB file.
Fixed #4162

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Doc#umentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[x] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

changes done. kindly review the PR
@prathimacode-hub


text:
Publish Maps Notebook 24 - Datapane - Invalid version 'unknown'

Thanks for these lessons and videos. A great resource.
Environment Information

geemap version: 0.8.14
Python version: 3.9.2
Operating System: macOS 10.15.7

Description
I am trying to run the Example notebook 24 Publish Maps https://github.com/giswqs/geemap/blob/master/examples/notebooks/24_publish_maps.ipynb
What I Did
I signed up and created a Datapane account and followed all the cells from your notebook.
To confirm datapane is set up I ran:
import datapane as dp
dp.ping()

Response:
Connected successfully to https://datapane.com as {username}

Where it breaks is here:
Map.publish(name='gee_folium_map', headline='Terrain Visualization', visibility='PUBLIC', overwrite=True)

Response:
Invalid version: 'unknown'

Thanks for reporting. The recent datapane release changes the API and some parameters for the publish functions are no longer valid. This bug has been fixed. Please update geemap using geemap.update_package() and try the following.
https://github.com/giswqs/geemap/blob/master/examples/notebooks/24_publish_maps.ipynb
Map.publish(name='Terrain Visualization', description='A folium map with Earth Engine data layers', visibility='PUBLIC')

hello,Mr.wu.
It seem that i got the similar problem in the 24_publish_maps.ipynb which is shown in the following.
env
geemap version: 0.9.4
Python version: 3.9.7
Operating System:Ubuntu 20.04.3 LTS
run and  got

authors: chichizhao giswqs nygeog

repo: giswqs/geemap


text:
Added git diff --staged to be synonym for git diff --cached

Sorry for the incomplete PR last time.
Here you go 😄

You may put the or part in the alternatives attribute like this thank you.

I added it in the alternatives but however the README doesn't seem to be updated. Anything I did wrong ?

Good catch! Can you have a look at this and see what's messed up?

@hemanth The glaringly obvious issue was that I haven't included it in an array. So that's why it didn't work. Should be fixed now

authors: Ranhiru hemanth

repo: git-tips/tips