New Term - vitality

New term

Submitter: Sophia Ratcliffe

Efficacy Justification (why is this term necessary?): There is a requirement that species records express whether the organism was dead or alive at the time of the observation or collection. Currently no such explicit term exists in Darwin Core.

Demand Justification (name at least two organizations that independently need this term):

NBN Trust
Ocean Biodiversity Information System (OBIS)
The Field Museum
Global Genome Biodiversity Network (GGBN)

Stability Justification (what concerns are there that this might affect existing implementations?):  None

Implications for dwciri: namespace (does this change affect a dwciri term version)?: The term dwciri:vitality will be created simultaneously with the term in the main DwC namespace: dwc:vitality.

Proposed attributes of the new term:

Term name (in lowerCamelCase for properties, UpperCamelCase for classes):  vitality
Organized in Class (e.g., Occurrence, Event, Location, Taxon):  Occurrence
Definition of the term (normative): An indication of whether the organism was alive or dead at the time of collection or observation
Usage comments (recommendations regarding content, etc., not normative): Recommended best practice is to use a term from the controlled vocabulary intended to be used with this term, listed at http://rs.tdwg.org/dwc/doc/vit/ Generally intended to be used with a dwc:basisOfRecord of PreservedSpecimen, MaterialSample, or HumanObservation.
Examples (not normative, for the dwc: namespace term only): alive, dead, mixedLot, uncertain, notAssessed
Refines (identifier of the broader term this term refines; normative): None
Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): None
ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): I was not able to find an equivalent term

The Vitality Controlled Vocabulary to be used as values for this term can be viewed here (note: the URL listed in the comments will not dereference until after ratification). dwc:vitality will use the controlled value string for the appropriate concept in this vocabulary as its value. dwciri:vitality will use the unabbreviated term IRI as its value.

We will submit a proposal for a causeOfDeath extension in due course.

Because shells persist for thousands to millions of years after the death of the animal who formed it, whether the specimen was collected alive can be important to understand the distribution in time and space of LIVING individuals of species.

I'd reiterate TimAPearce: if we know whether the specimen was collected alive or dead and can add that information to the specimen record, that can help researchers using the data understand more about the biology of the organism.

I support this in the strongest possible way.  Because of the long-term persistence of calcareous skeletal material (e.g., molluscan shells) these may have been dead for decades or even centuries when collected.  Such data are obviously suspect when used in discussions/maps of recent changes in faunal distributions.  We need to find a meaningful way to flag live/dead-collected specimens and have that distinction readily piped to relevant data aggregators.

Plus one here, others have already made the case well enough.

Thanks to everyone for their work on this- I support it

Other organizations that need this term include iNaturalist, which has an attribute of "Alive" or "Dead" and the Academy of Natural Sciences of Philadelphia (ANSP). Currently more than 3.5 million observations in iNaturalist are annotated for this attribute, including 125,000 for mollusks. The malacology database as ANSP also supports the live dead distinction, which has been made for 56,000 samples.

The distinction between live/dead is a key problem for the entire molluscan community because it affects the usability/fidelity of mollusk-based biodiversity records. Dead-collected shells can be hundreds of years old; therefore, their records
would not be useful in addressing short-term questions related to climate change or range extensions.

@gparosenberg wrote:

Other organizations that need this term include iNaturalist, which has an attribute of "Alive" or "Dead" and the Academy of Natural Sciences of Philadelphia (ANSP). Currently more than 3.5 million observations in iNaturalist are annotated for this attribute, including 125,000 for mollusks. The malacology database as ANSP also supports the live dead distinction, which has been made for 56,000 samples.

I  note that iNaturalist also has "evidence of recent life" to convey something was alive not too long ago (as opposed to a shell that's been there for who knows how long which could be more of a "relict" idea).

@rbieler @fmrdelapena what other collections (outside mollusks) would / could use this term meaningfully? As you put it so nicely in a use case Robin, known it is/was recently alive (until collected anyway) then the data is fit for use in addressing range extension assessment (for example). Are there other collections, that could use this similarly? (Doesn't really seem to work for herbarium specimens -- they are all (I think?) alive at time of collection by default).  But would this distinction work for other collection types that can then support a research purpose?

@debpaul This would apply to many of the calcareous skeletons in our (proverbial) closets of "dry" collections -- corals, bryozoans, brachiopods, foraminiferans, etc.

> unable to determine
The functional metabolism of the organism is not possible to determine

I do wonder about the use of this term. It seems like unknown would cover this, and adding it in will lead to confusion between when a collection chooses to use one or the other term.

Since the vitality field (or fields) can often be determined after collection, I would add another term: "not yet determined."   It seems to me, because this is a new field (or fields), the first entry for all existing dry preserved records would be "not yet determined". In practice, I don't see that every specimen within a lot will be evaluated. In my mind, the question is, Is there at least one specimen in the lot that was collected live?  Conceivably a specimen lot could have specimens that were live collected, dead collected, "not recorded" and "unable to determine"  I'm having a hard time seeing what the fields will be here. Is there one Vitality field with the above terms and they are check boxes? I don't think that is very informative for Queries/Searches. Are the fields dead, alive and not recorded? And the alive and dead fields have values of True, False and unable to determine and not yet determined?  I think that is a lot of checkboxes. Or, because the primary question is whether or not there is at least one live specimen, there are two fields only: Alive and Not recorded. Where the alive field is T, F, not yet determined or unable to determine. That seems simplest of all. A field that indicates at least one specimen was collected live. My apologies if this is dealing too specific for this thread. I'm just trying to see how this is going to look in practice.

@ekools For our Thematic Collections Network project (Eastern Seaboard mollusks), we have agreed - at the collections end - to record the following for each lot:

live [when collected]
dead [when collected]
live + dead [= mixed lot]
uncertain [= can’t currently tell after visual inspection; use comments if needed]
not assessed [or empty entry, depending on database system used]

Because of the wide variety of database systems involved in our project (EMu, Specify, Arctos, Filemaker, etc.) we are still working on the collections-level implementation of the above.  We understand that our desired collection-level distinction might be too detailed to pass on to aggregators, so we could readily combine them into a smaller number of items (e.g., live [including mixed lots] / dead [only] / unknown -- or  live / dead/ unable to determine / unknown) once such an option exists

@debpaul:  I agree - not sure this term would find much use in the herbarium community.

I'm fascinated and also a little worried if I come across a vertebrate object that would use either of the:

live + dead [= mixed lot]

uncertain [= can’t currently tell after visual inspection; use comments if needed]

I'm sure IACUC would have words with me...

Thank you, @rbieler  I think in practice we would focus on whether or not there is a live collected specimen, eliminating the need to evaluate each specimen. So, would lean towards your last example and eliminate the live + dead field as this could be indicated by a True Value in both the live and dead collected fields. The field Not Recorded is interesting because it indicates the evaluation was made after collection. Fun stuff. Thanks!

I support the use of this term as currently defined. It would be useful in the entomological collections community, as we mostly collected specimens alive and kill them, but occasionally find "preservable" specimens that died recently, but it would be useful to have this term in order to indicate that it was not alive at time of collection, and therefore should not have bearing on things like phenology, etc ...

@debpaul -- In some cases entomological collections could use this term.  I myself have collected quite a bit of material where the specimen was found dead.  Currently, we use "hand collected" as the collection method and "found dead" as the detail.  Since many arthropod's life cycles are annual its would be easier to assume its "age".   On the other hand, if a season or two has passed, a dead insect specimen would most likely have deteriorated from the elements and wouldn't be worth collecting anyway.

For vertebrate collections you may want to talk to eBird, iNaturalist, and the Zoo community. They will have the largest sample sets currently that may get listed as Live. The majority of vertebrate museum specimens currently are going to be dead. This may change as we work with more behavioral researchers, but the full vouchered specimens are still going to come into our collections already expired.

All of the vitality qualities possible in different kinds of collections need not be specified as a list item for a
"vitality" classification to carry important specimen information, viz. the example noted above, of mollusk shells
surviving their owners and possibly being transported far from their origin.  Additionally, the collection of living
specimens has different legal and provenance implications depending on the date of collection.  A researcher
wishing to use data can sort by vitality category to eliminate, for example in the above two cases, specimens
of dubious geographic origin or specimens illegally collected.  The finer points of vitality relevant to particular
types of collections might be added as subsections, or preserved in narrative fields.  OP's proposal seems sound.

I don't have a set of cause of death terms, but I've been able to score more than 60,000 records in our malacology collection database for vitality based on information in the records. If cause of death were also recorded when known, that would increase the usefulness of the data. In our Eastern Seaboard TCN, we are interested in whether an observation gives evidence that a species lived at a site on a particular date. If, for example, one observes a seagull carrying a clam and dropping it on rocks, the observation gives evidence that the clam lives in the area. If the fragments are collected, however, they would be scored as dead. Our project has experimented with two fields, "vitality" and "means of inference", but not a "cause of death" field.
"Cause of death" would presumably refer to death other than that caused by preservation of the specimen in a collection. If one has a collection that includes living items, perhaps that could be indicated here as "still living", to distinguish current vitality from vitality at time of collection.
On iNaturalist, the instructions are that if something is moribund, it should be scored as dead. Whether that is appropriate depends on the question being asked. When I see whelk egg cases washed up on a beach, scoring them as dead seems appropriate, although further investigation might reveal that some of the egg cases contain juvenile snails that are still alive. Nonetheless, they would almost certainly die soon, because they are stranded on the beach. Maybe it would be better to score them as "cannot be determined", which is one of the values allowed by iNaturalist. Even that depends on context. The person who made the observation would have more information than a subsequent person evaluating the image to decide if it should be scored as live or dead.
I'd advocate having a controlled vocabulary that allows considerable granularity, because different researchers have different questions. We have tested "live", "possibly live", "fresh dead", "dead", "long dead", "subfossil", and "fossil". The latter two turned out to be useful only as "means of inference". If the record stated a specimen was subfossil or fossil, it can be scored as dead. How long something has been dead is a different axis.
"Possibly live" versus "fresh dead" allowed us to preserve distinctions. If we have bivalves that are paired (valves still attached by ligament), it might be that they were collected alive and killed by the collector, or they might have been found dead on the beach, still paired. If the collector recorded this information, the scoring as live or dead is easy. If the information was not recorded, it can be difficult to infer, although it is sometimes possible, for example if bits of tissue adhere to the shell, one could infer that it was live-collected. A later observer could choose "possibly live", when they are unable to make the distinction or don't have time to do it.  Someone using the data could then decide if they want to include "fresh dead" and "possibly live" observations, depending on the question they were asking.
Some of our lots have a mixture-some specimens live-collected and some dead-collected. For these it would be useful to have an option for "live and dead". I prefer this to two separate flags, one for live and one for dead, because if both were checked, that would immediately raise the question of whether there was an error in data entry.
Looking at our means of inference field, for items flagged as fresh dead, I see several items relevant to a list of causes of death: eaten by a bird or fish, dropped on road by seagull, drilled by a muricid, naticid or octopus, found drowned
Best wishes,
Gary
From: Sophia @.>
Sent: Monday, November 15, 2021 11:02 AM
To: tdwg/dwc @.>
Cc: Rosenberg,Gary @.>; Mention @.>
Subject: Re: [tdwg/dwc] New Term - vitality (#363)
External.
Thanks for all your comments. We have a working session on Wednesday (17th) at 17.30 UTC, hopefully many of you can join. The agenda is here: #363https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftdwg%2Fdwc%2Fissues%2F363&data=04|01|rosenberg.ansp%40drexel.edu|f190d98d28d9488454ef08d9a8514de8|3664e6fa47bd45a696708c4f080f8ca6|0|0|637725889428900051|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=WQTeegBaBSVTPpUwr9HxJMlebHWBOW6YfNj646EwDOA%3D&reserved=0
Does anyone have a dataset with cause of death terms that we could test against our proposed controlled vocabulary?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftdwg%2Fdwc%2Fissues%2F363%23issuecomment-969057628&data=04|01|rosenberg.ansp%40drexel.edu|f190d98d28d9488454ef08d9a8514de8|3664e6fa47bd45a696708c4f080f8ca6|0|0|637725889428900051|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=F2vJgJb7fOhlCHpNM7R46%2FXn0AF5Dt0AcaCemENzm7M%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAVUXHXXOV5QKM72KNO2CF73UMEVIXANCNFSM5A2F572A&data=04|01|rosenberg.ansp%40drexel.edu|f190d98d28d9488454ef08d9a8514de8|3664e6fa47bd45a696708c4f080f8ca6|0|0|637725889428910010|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=AZuVo17bDEVESQXuq9Pc41PCUIz0z6lsKmcLoVFUATo%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|rosenberg.ansp%40drexel.edu|f190d98d28d9488454ef08d9a8514de8|3664e6fa47bd45a696708c4f080f8ca6|0|0|637725889428919965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=U9vpat%2FYyk38XDxsgzQRc5CAQ6buABOln%2Bjl2Wm6yfs%3D&reserved=0 or Androidhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|rosenberg.ansp%40drexel.edu|f190d98d28d9488454ef08d9a8514de8|3664e6fa47bd45a696708c4f080f8ca6|0|0|637725889428919965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=QNlE4xHJ%2Bp8oCg85ODH53IK7OpqvINa3TEWksPsGoeE%3D&reserved=0.

In consultation with the Task Group convener and in preparation for this going to public comment, I have formalized the Task Group's recommended values into a formal controlled vocabulary that can be viewed here: https://github.com/tdwg/rs.tdwg.org/blob/vitality/process/page_build_scripts/vitality.md.
As a consequence, I edited the original term proposal to match the style of other terms that have officially designated controlled vocabularies. I also edited the examples section (for the dwc: namespace analog) to match the controlled value strings as listed in the controlled vocabulary. I also made a note (consistent with existing DwC policy) that a dwciri: term would be minted simultaneously with the dwc: term and that the term IRIs from the controlled vocabulary would be used as its values.

This issue has accumulated massive support, but there remain unresolved issues with respect to consensus, at least as captured in this particular issue. Does the Task Group have a recommendation that addresses all of the concerns expressed here?

I thought the same thing as Quentin.

In re-reading the thread, I still wonder why we're not re-using the physiological state from PATO (see https://github.com/tdwg/dwc/issues/363#issuecomment-949961320).
Especially after reading the examples described in:
https://github.com/tdwg/rs.tdwg.org/blob/vitality/process/page_build_scripts/vitality.md

Label
dead

Definition
The state where the organism has irreversible loss of functional metabolism at the time that the observation or collection was made

Label
alive

Definition
The state where the organism has functional metabolism at the time that the observation or collection was made

To me, vitality seems to suggest some kind of quantitative score between alive (e.g., 10) and dead (e.g., 1). and I think describing a physiological state may be a little more nuanced than that.
Inventing new terms is easy, but keeping them is . . . time intensive! (e.g., https://github.com/oborel/obo-relations/issues/368 - a new term request is still ongoing after first being proposed in 2020). So, I favor re-use of existing terms.
my 2 cents.

I realize that the public review is for the proposal as it currently stands, and that there were no explicit objections during the public commentary period. However, there are comments from prior to the public review for which it is not apparent that they were ever addressed, and the outcomes if they were is not in evidence. Here are the specific comments in question:
https://github.com/tdwg/dwc/issues/363#issuecomment-949961320
https://github.com/tdwg/dwc/issues/363#issuecomment-953631051 and
https://github.com/tdwg/dwc/issues/363#issuecomment-954153258. There was some discussion about the name vitality, with "viability" "physiologicalState" as options. The latter (as "pato:physiological state") seems to cover the same concepts and is used in several ontologies. A poll proposed was mentioned, but no results of that poll were shared.
Others were discussions about vocabulary values (whose final proposed values can be seen at https://github.com/tdwg/rs.tdwg.org/blob/vitality/process/page_build_scripts/vitality.md.
Many of the comments about the proposed vocabulary seem to have been addressed, but not all, at least in this issue. For example,
https://github.com/tdwg/dwc/issues/363#issuecomment-970569151
It would be good to know if these comments were addressed anywhere, and what the outcome was.

All of these fields pertain to data from the observer/collector.  Why not include the Inferred Data in the same Vitality Scheme ?

I've seen a similar term described at "physiological state", with terms from ontologies like PATO:
term name	term IRI
dead	http://purl.obolibrary.org/obo/PATO_0001422
alive	http://purl.obolibrary.org/obo/PATO_0001421
Examples in GloBI would be something like:
Jane saw a cat eating a dead mouse.

The PATO definitions of dead and alive are quite similar, though they are under PATO viability which is different from the definition of vitality.
viability

An organismal quality inhering in a bearer or a population by virtue of the bearer's disposition to survive and develop normally or the number of surviving individuals in a given population.

vitality

An indication of whether the organism was alive or dead at the time of collection or observation.

I'm not sure the difference in definition of the parent matters, but other siblings of viability would not be suitable, such as immortal, lethal and semi-lethal.

How did you come to the name vitality?
After a great deal of toing and froing and compromising ;-)

In the Eastern Seaboard TCN, we have recommended adding fields to record means of inference of the vitality status. Also, because mollusk collections usually catalogue by lots rather than individual specimens, we've found that it might speed assessment to allow additional values beyond "live" dead" and"uncertain". Ech of the items below can be mapped to one of the three main values .
Live and dead: Both live and dead collected specimens are in the lot. Maps to "live"
Possibly live: at least one specimen might have been live collected. Indicates that the specimen is in good enough condition that it might have been alive when collected. Maps to "Can't be determined"
Fresh dead: no specimen in the lot was live collected, but at least one is known to have been fresh dead (e.g., valves of bivalves still attached by ligament). Maps to "Dead".
Best wishes,
Gary
From: ekools @.>
Sent: Friday, March 31, 2023 12:44 PM
To: tdwg/dwc @.>
Cc: Rosenberg,Gary @.>; Mention @.>
Subject: Re: [tdwg/dwc] New Term - vitality (#363)
External.
@qgroomhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fqgroom&data=05|01|rosenberg.ansp%40drexel.edu|90cad11cb7844548bc0f08db32071b50|3664e6fa47bd45a696708c4f080f8ca6|0|0|638158778376605406|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=xVkM2r5ZmN0gNPNNdnvf%2BIYzVjz0DaVC1LrCXN%2FG6xI%3D&reserved=0 Yes. It is clear from the discussions that data pertaining to the vitality of organisms at the time of collection or observation is needed. However, the definitions developed for the Vitality Scheme appear to rely solely on data recorded at the time the observation or collection was made. The vast majority of dry preserved material held in museums does not have this data recorded by the collectors. This does not mean that this data cannot be inferred. I think the scheme (or individual databases) can take this into account by indicating the "source" of the data. It is either the collector, or another "Agent".
For the definition of "uncertain" "The functional metabolism of the organism was not possible to determine at the time that the observation or collection was made" would be changed to read "The functional metabolism of the organism (at the time of observation or collection) is not possible to determine."
The term "not assessed", defined as "The functional metabolism of the organism was not recorded at the time that the observation or collection was made" would be changed to "The functional metabolism of the organism has not yet been determined or assessed."
I think it is the order of the wording that is throwing me off. For alive, it is easier for me if "The state where the organism has functional metabolism at the time that the observation or collection was made" reads "The state where the organism (at the time of observation or collection) had functional metabolism.
I also think that persons using data available in the aggregators are going to find "Evidence of Recent Life" and/or "Recently Alive" (=fresh dead) of immense value and we want to include them in the definitions. The term aestivating may also be included too. I'm not sure.
Hope that is clear.

Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftdwg%2Fdwc%2Fissues%2F363%23issuecomment-1492251981&data=05|01|rosenberg.ansp%40drexel.edu|90cad11cb7844548bc0f08db32071b50|3664e6fa47bd45a696708c4f080f8ca6|0|0|638158778376605406|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=IV19zWrMrljjyRjUrtWx3snUm6yPXkbukRMyyEdXVR8%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAVUXHXUGJ3LKKT7CYJUTMTDW64CUNANCNFSM5A2F572A&data=05|01|rosenberg.ansp%40drexel.edu|90cad11cb7844548bc0f08db32071b50|3664e6fa47bd45a696708c4f080f8ca6|0|0|638158778376605406|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=avX20uqnzz8LMSNS5F3kGD%2FKx4xDlYfJOIdFJia%2Bin8%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

For the definition of "uncertain" "The functional metabolism of the organism was not possible to determine at the time that the observation or collection was made" would be changed to read "The functional metabolism of the organism (at the time of observation or collection) is not possible to determine."

The term "not assessed", defined as "The functional metabolism of the organism was not recorded at the time that the observation or collection was made" would be changed to "The functional metabolism of the organism has not yet been determined or assessed."

I think it is the order of the wording that is throwing me off. For alive, it is easier for me if "The state where the organism has functional metabolism at the time that the observation or collection was made" reads "The state where the organism (at the time of observation or collection) had functional metabolism.

I don't think anyone would have a problem with those amendments.
The vocabulary is only a recommendation and non-normative, which is why I can't really understand why this causes a block to vitality be accepted, particularly when there is such obvious and immediate demand.

The issue is not blocked. It just requires consensus. Consensus has not been achieved for the reasons described here.
Examples of vocabulary terms would be non-normative, but given this comment, a formal vocabulary (normative) is also being proposed. Consensus has not been demonstrated on the controlled vocabulary.

But a consensus was formed by the task group. You will understand my frustration when we could have dispensed with a whole bunch of task group meetings if the consensus we built there doesn't really count for anything.
The comments by @gparosenberg, @jhpoelen  and @ekools don't even seem to conflict with the suggested controlled vocabulary.

I agree with Quentin. There are 24 thumbs up and many people saying they would use this term once available. I guess I'm confused how three mild suggestions that are not even outright disagreements means there is not consensus. How long do we have available to provide responses from the task group to what's been outlined here to still get this term approved during this public commentary period? I have a dataset that cannot be shared until this term is available and I would really like to move that one forward if I can.

I think a bit of explanation would help this issue. The goal of the task group is to define terms for the question "How did it die?" We are discussing many other terms with their own vocabularies to expand this set of terms. The goal with the term Vitality is to expedite the acceptance of a single term the for which the community has expressed an immediate need. Once we have the basic question of if an organism was dead or live at the time of observation/collection, we can expand the terms for use by, among others GGBN.  Physiological State is a much broader term then what we are hoping to achieve with Vitality.

If the problem is only with the controlled vocabulary itself, it seems to me that the vitality term itself could be adopted with additional work on the controlled vocabulary later. We have plenty of terms in Darwin Core for which a controlled vocabulary is not (yet) available. I haven't paid close enough attention to the discussion of the controlled vocabulary to know what the issue is with it, but if it is an issue with missing values, they can be added later. If it's an issue with non-critical proposed values, they could be removed, leaving the critical ones.
It is frustrating to me when the perfect becomes the enemy of the good. That seems to be a common problem with Darwin Core proposals. It leads to frustration and cynicism on the part of people who put in a lot of work on a proposal and we risk losing the participation of those people in future efforts if they feel the time they've expended doesn't pay off.
This proposed term has been languishing for a long time and there's huge demand for it. If there is a way to cut out or fix the aspects of the propose that lack consensus, we should do it and get at least the term itself adopted.

I am sorry - I realised that I didn't add the notes from the TDWG 2021 working session, where we had a poll on the name of the term.
I've uploaded the group chat and meeting notes here: https://github.com/tdwg/how-did-it-die/tree/main/meetings/TDWG 2021 WG session
The options for the poll were: 1. vitality, 2. viability and 3. physiological state. Nine people voted (there were only 12 in the session), results:
vitality 5
viability 1
physiological state 3
It was agreed to continue with vitality as the term name and to add the term 'mixed' to indicate collection lots of both live and dead organisms.

For the definition of "uncertain" "The functional metabolism of the organism was not possible to determine at the time that the observation or collection was made" would be changed to read "The functional metabolism of the organism (at the time of observation or collection) is not possible to determine."
The term "not assessed", defined as "The functional metabolism of the organism was not recorded at the time that the observation or collection was made" would be changed to "The functional metabolism of the organism has not yet been determined or assessed."
I think it is the order of the wording that is throwing me off. For alive, it is easier for me if "The state where the organism has functional metabolism at the time that the observation or collection was made" reads "The state where the organism (at the time of observation or collection) had functional metabolism.

I am happy for the definitions to change, as described above.

I also think that persons using data available in the aggregators are going to find "Evidence of Recent Life" and/or "Recently Alive" (=fresh dead) of immense value and we want to include them in the definitions. The term aestivating may also be included too. I'm not sure.

We did discuss including dormant in the vocabulary, but the organism is alive - and we wanted to keep the term as simple as possible for the most practical use.
The date of death is going to be covered in the cause of death extension proposal and the group agreed that 'recently alive' or 'freshly dead' could be covered by the date of death. If there is a use case of including it in the vocabulary then we can consider it again, but we should be clear what recent or fresh means.

Thanks @sophiathirza for the Task Group background information. Looking through the thread it seems that the justification for the choice of term name has been met. All other open discussion is about the controlled vocabulary. It also seems there is clear and immediate use for the term even without the associated formal controlled vocabulary. I'll change the status of this issue to "Ready for Executive Review" and start to prepare the entire package.
A new issue should be created to move forward with the controlled vocabulary, and should reference this issue as background and the source for remaining issues that need to be resolved.
Thank you everyone for your efforts and patience. Progress!

Huzzah!

For those of you interested in a causeOfDeath term I have added a specific term request here https://github.com/tdwg/dwc/issues/521
Please give it some support with comments and a 👍


SonarQube Found 5 Blocker Code Smell Issues

What problem does this feature solve?
1.
{
  strats.el = strats.propsData = function (parent, child, vm, key) {
    if (!vm) {
      warn(
        "option \""   key   "\" can only be used during instance "
        'creation with the `new` keyword.'
      );
    }
    return defaultStrat(parent, child)
// Move the declaration of "defaultStrat" before this usage.
// L1127 Code Smell Blocker
  };
}
// Declaration L1326
var defaultStrat = function (parentVal, childVal) {
  return childVal === undefined
    ? parentVal
    : childVal
};

2.
new Watcher(vm, updateComponent, noop, null, true /* isRenderWatcher */);
// Move the declaration of "Watcher" before this usage.
// L2795 Code Smell Blocker
// Declaration L3082
var Watcher = function Watcher (
  vm,
  expOrFn,
  cb,
  options,
  isRenderWatcher
)

3.
var normalizedName = normalize(name);
// Move the declaration of "normalize" before this usage.
// L7275 Code Smell Blocker
// Declaration L7292
var normalize = cached(function (prop) {

4.
if (def.css !== false) {
	extend(res, autoCssTransition(def.name || 'v'));
// Move the declaration of "autoCssTransition" before this usage.
// L7427 Code Smell Blocker
}
// Declaration L7436
var autoCssTransition = cached(function (name) {

5.
var end = function () {
	el.removeEventListener(event, onEnd);
// Move the declaration of "onEnd" before this usage.
// L7513 Code Smell Blocker
	cb();
};
// Declaration L7515
var onEnd = function (e) {
	if (e.target === el) {
		if (  ended >= propCount) {
			end();
		}
	}
};

What does the proposed API look like?
SonarQube Explanation
Variables should be declared before they are used
Variables declared with var have the special property that regardless of where they're declared in a function they "float" to the top of the function and are available for use even before they're declared. That makes scoping confusing, especially for new coders. To keep confusion to a minimum, var declarations should happen before the variables they declare are used for the first time.
Noncompliant Code Example
var x = 1;
function fun(){
	alert(x); // Noncompliant as x is declared later in the same scope
	if(something) {
		var x = 42; // Declaration in function scope (not block scope!) shadows global variable
	}
}
fun(); // Unexpectedly alerts "undefined" instead of "1"

Compliant Solution
var x = 1;
function fun() {
	print(x);
	if (something) {
		x = 42;
	}
}
fun(); // Print "1"

Please do not automatically open issues like this.
It's fine if you use a tool to get some guidance, but at least provide a repro illustrating the problem or do some summarising instead of just copy pasting the whole thing. Thank you


Enter/Exit claim message does not show in action bar

message {
# The default chat type to use when sending enter/claim messages to a player.
# (0 = Chat, 1 = ActionBar, 2 = Title)/nNote: ActionBar is only available in MC 1.11+
enter-exit-chat-type=1
# Whether GD prefix should be shown in enter/exit claim messages. (Default: true)
enter-exit-show-gd-prefix=true
# Set the locale to use for GD messages. (Default: en_US)
# Available languages: de_DE, en_US, es_ES, fr_FR, ru_RU. The data is stored under assets in jar.
# Note: The language code must be lowercase and the country code must be uppercase.
locale="en_US"
}

The message still appears in chat, not the action bar.

Title does not work either, I believe it was explained that KyoriText has not implemented this yet.

This was a bug in kyori and should work in GD 1.4.4 as kyori was updated to latest.


Add SpotMarketRequests resources

Description of your changes
This is a work-in-progress (likely doesn't compile).
This adds support for the Packet Spot Market.
Questions:

How do you provision and access SpotRequestResources devices?

Does provisioning depend on existing Project SSH Keys?

How do cluster centered resources take advantage of this?
Is a new SSH Key resource required? (to generate keys and add them to the project)

Running SSH with password auth, from a docker container, takes some hoops.

Do we need an independent SSH runner resource? (like https://github.com/crossplane-contrib/provider-helm, thanks for this reference @hasheddan)
Does provisioning depend on cloud-init?

How do you interact with the created devices in a standard way?

Should Device resources be spawned by SpotRequestResources?
How do you power-off/create/destroy these nodes?

Importing these nodes as new Devices through external-name references will cause them to be recreated independent from their spotmarketrequest (not desirable).  Devices do expose a spotrequest flag - could this influence the controller behavior to not recreate deleted devices?  Would the device hold a reference to the spotrequest resource?

Checklist

I have:

[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the package resources documentation and app.yaml to include any new managed resources or classes.

Closing for #69
Implemented in https://github.com/crossplane-contrib/provider-jet-equinix


Allow to fully archive a share with one click

There are situations when a share is no longer needed. In such a case a user has to manually revoke all items, wait for them to get processed and then delete the share. This user experience could be better. I would like to be able to archive / delete a share with a click of a single button.
If a share is not possible to delete because of issues I'd like to receive an email notification that a share was not possible to delete (for example some because some item could not be revoked)

Hi @zsaltys thanks for opening this issue - for both adding share items and revoking share items we can look to support a way to add/revoke multiple items in batch. I am thinking similar to the checkbox selection we have for something like verify share items or re-apply
In that case a user can revoke all items in one pass and then delete the share if no complications on revoke
Let me know if you are thinking differently
For notifications - let's use the parent issue #1420 to determine all events where we want outbound notifications on and can implement a generic way to do so?


make the reason why 0860 (form history) is disabled clear to end-users

/* 0860: disable search and form history
 * [NOTE] You can clear formdata on exiting Firefox (see 2803)
 * [SETTING] Privacy & Security>History>Custom Settings>Remember search and form history ***/
user_pref("browser.formfill.enable", false);

compare that to
/* 0862: disable browsing and download history
 * [NOTE] You can clear history and downloads on exiting Firefox (see 2803)
 * [SETTING] Privacy & Security>History>Custom Settings>Remember browsing and download history ***/
   // user_pref("places.history.enabled", false);

WHY allow one but not the other? We relaxed the urlbar dropdown (to E's delight) - that's all the  0850* prefs, and this is another one that relates to "shoulder surfing" which I think goes too far - very little benefit but causes loss of usability. Note that we already clear form & search on close. So I don't really see the point in disabling the feature
I want to make this inactive (i.e existing users will not get any nasty surprises when they update, as they would have to manually clear it in about:config)
^^ This (forms & search) along with #690 (auto-updating extensions) are about the two biggest warnings in the implementation page. So it would be nice to do away with them - just like we changed from blocking all cookies to allowing 1st party. The less scary the wiki implementation the better
From the wiki

Since FF55 we disabled search & form history

^^ I think E talked me into that one, but I do not recall the logic behind it - except that I don;t use it, so I might have just gone along with it. I do not believe forms are any more dangerous that download/search/places/urlbar history etc. So lets be consistent
Once again 24 hrs to change my mind :) (psst! @earthlng waiting on your input on these two issues)

I do not believe forms are any more dangerous that download/search/places/urlbar history etc

the difference is that form data can easily be stolen fe see https://www.ghacks.net/2011/10/25/browser-autocomplete-feature-may-reveal-personal-data/
I just tested it and it was able to read my form data which I entered on another site, so yeah this is still very much a problem IMHO.

Nice PoC. Even running in a different container reveals data.
I vote for active set as false... as it is now.
Cheers

the difference is that form data can easily be stolen

Ahh, I knew there was a reason - thanks. Hence why I said "change my mind". I'll check that link a little later - but I'm glad I revisited this. In the back of my mind I thought these sorts of things would have been mitigated by now. e.g forms not auto-filling until you start typing in them etc - in which case you would probably want the data in there anyway (I was thinking of usernames, addresses, postcodes etc). And other changes in FF since 2011 (date of the link) to tighten this shit up - like I said, I need to read that link.
Anyway, to stop the BS'ery that is caused by some people not reading, we should at least included a reason for why 0860 is disabled in the js and on the wiki page (which I want to slightly revamp - as it seems people see the first warning about SB+TP and assume we turned it off) - so I'll use this ticket to do that

OK, I just quickly read that, and I'll dig later - but it only talks about "autocomplete". I though "auto" was all disabled via other means. It certainly is AFAIK for logins/password fields, which must be treated separately, as I type the first letter of my username to bring up the data.


test: Fix encryption scheme checks in tests

Use the uncompiled encryption scheme polyfill, for consistency, when running unit tests against the uncompiled library source.
Upgrade the encryption scheme polyfill to a version that is resilient against multiple copies (one in compiled shaka library, one in source form).

It seems that the new version breaks the DRM in Firefox and does not work.

Also it produces an error in Tizen:

 Safari 3.0 (Tizen 3.0) ERROR
  An error was thrown in afterAll
  Uncaught SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
  SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

@shaka-bot test


Routing not working with special character in UpstreamPathTemplate

Hi,
we're using ocelot as an API gateway for a service using OData. In OData, one feature is to have a route with $query in the name.
For example: /v3/Orders/$query
Here is the documentation for that specific thing :  https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_PassingQueryOptionsintheRequestBody
Expected Behavior / New Feature
Having the next route exposed in Ocelot and being able to call the $query route on the underlying service.
{
  "UpstreamPathTemplate": "/v3/Orders/$query",
  "DownstreamPathTemplate": "/v1/Orders/$query"
}

Actual Behavior / Motivation for New Feature
A 404 is returned with those warnings in the logs:
[13:10:56 WRN] requestId: , previousRequestId: No PreviousRequestId, message: 'DownstreamRouteFinderMiddleware setting pipeline errors. IDownstreamRouteFinder returned Error Code: UnableToFindDownstreamRouteError Message: Failed to match Route configuration for upstream path: /v3/orders/$query, verb: POST.'
[13:10:56 WRN] requestId: , previousRequestId: No PreviousRequestId, message: 'Error Code: UnableToFindDownstreamRouteError Message: Failed to match Route configuration for upstream path: /v3/orders/$query, verb: POST. errors found in ResponderMiddleware. Setting error response for request path:/v3/orders/$query, request method: POST'

Steps to Reproduce the Problem
See previous sections. Using the '$' character in the upstream route.
Workaround
Remove the $ character from the upstreamPathTemplate, but it won't respect the OData protocol.
{
  "UpstreamPathTemplate": "/v3/Orders/query",
  "DownstreamPathTemplate": "/v1/Orders/$query"
}

Specifications

Version: <IP_ADDRESS>
Platform: .NET 8
Subsystem: Windows

This issue is probably related to

#2116
#2132

but I'm not sure

Having the next route exposed in Ocelot and being able to call the $query route on the underlying service.
{
  "UpstreamPathTemplate": "/v3/Orders/$query",
  "DownstreamPathTemplate": "/v1/Orders/$query"
}

I concur that all static routes with special characters should be functional and forwarded. However, I'm curious about the rationale for defining a static route.
Why not utilize placeholders and convert templates instead?
{
  "UpstreamPathTemplate": "/v3/Orders/{query}",
  "DownstreamPathTemplate": "/v1/Orders/{query}"
}

or even more short version?
{
  "UpstreamPathTemplate": "/v3/{everything}",
  "DownstreamPathTemplate": "/v1/{everything}"
}

Why don't you utilize placeholders?

OData query is supported via using placeholders, see examples in code & docs
My old answers in discussions with the same problem.

Duplicate of #859

Thank you, it worked.

Reopen to address triple:

this #2143
#859
#1930

@int0x81, welcome to your assignment!

@int0x81 @ggnaegi What's the progress here?


[WIP] Refactor to support running palm outside of an initialized git project

Pull request checklist
Before submitting your PR, please review the following checklist:

[ ] Consider adding a unit test if your PR resolves an issue.
[ ] All new and existing tests pass locally (palm test)
[ ] Lint (palm lint) has passed locally and any fixes were made for failures
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)

Breaking changes

[ ] Check if this pull request introduces a breaking change

What does this implement/fix? Explain your changes.

Use discover_repository to allow us to raise and handle a custom exception in the case we are outside of a git repo
Change the implementation of branch detection so that we have proper control over when that check is executed
Update the implementation of palm_config.plugins to be a list with setters
Implement a bare-bones 'setup' plugin as initial POC for the functionality

Does this close any currently open issues?
#12
Any other comments?
This is a WIP PR, still to be done:

[ ] implement new_machine
[ ] implement palm clone
[ ] document onboarding 'system' plugin commands
[ ] add tests around new functionality

Where has this been tested?
Operating System: Mac OS

What is the status of this PR?

What is the status of this PR?

This was a spike/RFC and thus far I've had no feedback on the approach. I think it is probably something we want to pursue, and I still quite like the direction this was going, but it's definitely a WIP

This work was re-done in #83 - conflicts here were too gnarly and I wanted to re-do some pieces of the implementation


Express server

Pull Request Test Coverage Report for Build 1365

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1356:
0.0%

Covered Lines:
44

Relevant Lines:
44

💛  - Coveralls


oic: Various fixes when using flow based programming

This commit fixes some problems that appeared during the update to the
newer version of the protocol, including some segmentation faults (due
to NULL pointer dereferencing), incorrect return values, CoAP encoding
errors, among other things.
It also updates the light-client.fbp example, illustrating the use of
the FOUND port to only enable the toggle timer if the light has been
found on the network.

I've tested with soletta-demos and it worked fine.
Changes make sense. It seems good.

Merged, thanks.


Enable full pip install of dependencies when testing

This removes all explicit dependencies on Python packages from all CircleCI testing environments.  This forces all packages to be installed by pip directly in the test environment, rather than depending upon the conda packages.

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   94.67%   94.67%
=======================================
  Files           6        6
  Lines         169      169
=======================================
  Hits          160      160
  Misses          9        9

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a592f0...563e1e5. Read the comment docs.


cranelift: Remove booleans

Remove the boolean types from cranelift, and the associated instructions breduce, bextend, bconst, and bint. Standardize on using 1/0 for the return value from instructions that produce scalar boolean results, and -1/0 for boolean vector elements.
Fixes #3205

I'm really happy that we're finally doing this! Thank you for taking this on.
Some of our lowerings depend on the fact that bools can only be represented as all ones or all zeroes, and so now that we are removing that assumption we might want to revisit them.
The AArch64 implementation for bmask is wrong if we want to accept any integer other than -1 and 0. (i.e. 2 will be false, but should be true)
bint is also assuming that inputs are all ones or all zeros and is implemented as and_imm on AArch64.

Also, just to note it here: if at all possible, I'd prefer for us to wait to merge this until after my mid-end work in #4953 is merged, if only because they're both large and likely-to-conflict PRs and mine has been through ~three painful rebases already :-)

@uweigand, could you take a closer look at my changes to the s390x backend? In particular the changes in c01d860, as they increased the instruction count for the bmask translation by quite a bit.

@uweigand, could you take a closer look at my changes to the s390x backend? In particular the changes to the lowering of bmask, as they increased the instruction count for the translation by quite a bit.

Well, in part this is due to changed semantics: the old bmask would take a boolean type as input, which (except for $B1) already used only the values 0 and -1.  So the semantics of bmask was simply a no-op or a sign-extend.  The new bmask I understand now needs to take any arbitrary integer input, so it actually has to perform a comparison against zero.
That said, I think the new implementation could still be improved, in particular the $I128 cases.  However, instead of re-implementing the wheel here, why don't you simply use the existing icmp_val helper to emit the actual comparison?
Maybe something alone the lines of
 (rule (lower (has_type oty (bmask x @ (value_type ity))))
       (lower_bool_to_mask oty (icmp_val $true (IntCC.NotEqual) x (imm ity 0)))

with a new helper lower_bool_to_mask analogous to the old lower_bool ...

Following up on myself, it would be even simpler and better to use the existing value_nonzero helper, which will fold in previous comparisons if possible:
 (rule (lower (has_type ty (bmask x)))
       (lower_bool_to_mask ty (value_nonzero x)))

Following up on myself, it would be even simpler and better to use the existing value_nonzero helper, which will fold in previous comparisons if possible:
 (rule (lower (has_type ty (bmask x)))
       (lower_bool_to_mask ty (value_nonzero x)))

This is much nicer! I'll rework the changes to add lower_bool_to_mask instead.

This is much nicer! I'll rework the changes to add lower_bool_to_mask instead.

Thanks!   The s390x parts LGTM now.


set rails loggers

Rails.logger works for most things and non-forking servers.
With forking servers like Puma/Unicorn however, classes like ActionView::LogSubscriber which are set to ActionView::Base.logger end up with an outdated reference post fork.
Set these loggers explicitly.

Worked well in my testing


ocaml-gen: implement safe unsigned values

Related to https://github.com/MinaProtocol/mina/issues/13224.
If we need real support for unsigned values, like u64 or u32, ocaml-gen must map to types like defined in ocaml-integers or ocaml-stdint. The values are implemented using custom blocks. Therefore, on the Rust side, the mapping must be custom blocks, not built-in types like u64.

ocaml-integers could be better as integers_stubs_js is already implemented


Will OrgAssetsLibrary still be supported?

Hi,
Non-Image file types will not be supported anymore, but what about the OrgAssetsLibraries?

https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/add-spoorgassetslibrary?view=sharepoint-ps
https://pnp.github.io/powershell/cmdlets/Add-PnPOrgAssetsLibrary.html

For example, the Org Assets Library "OfficeTemplateLibrary" is typically linked to a private CDN as it could contain a PPTX template with confidential client information - will that still be supported?
There is also a "ImageDocumentLibrary" that can be configured, but as the name indicates - it should contain images...
Kind Regards,
<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d6c9e87a-f0ca-b98a-96de-1ede59d58c21
Version Independent ID: d6c9e87a-f0ca-b98a-96de-1ede59d58c21
Content: Use Office 365 Content Delivery Network (CDN) with SharePoint Online - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/use-microsoft-365-cdn-with-spo.md
Service: microsoft-365-enterprise
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@kelleyvice-msft Please help us in resolving this issue. Thanks

Hi, Any update for this one?
NOTE: Even when we only focus on the Org Asset Library of type "ImageDocumentLibrary", which would still contain image content supported for the private CDN - the Add-SPOOrgAssetsLibrary command will by default use "Private CDN" which is no longer supposed to happen... we need to clarify this for our clients.

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Add workflows for MathComp 2.

As discovered when reviewing the update to deriving, lots of versions in coqPackages are currently untested because the default MathComp version is still MathComp 1 everywhere. With the addition of these two new workflows for Coq 8.17 and 8.18, we add these missing tests.
Note that ideally, we should avoid rebuilding packages which are unrelated to the MathComp ecosystem (packages that do not depend on MathComp and are not dependencies of other packages depending on MathComp), but I do not see any way to do this filtering other than manual. I tried the manual approach, but it was extremely tedious, and the filtering should evolve depending on what packages and package versions are available in coqPackages, which is not realistic if it is done manually.

It's interesting BTW, because the failures in this PR's CI show us which packages do not yet have a version compatible with MathComp 2 in nixpkgs. These are:

reglang (1.2.0 is not in nixpkgs yet)
extructures (fixed in https://github.com/NixOS/nixpkgs/pull/262791)
mathcomp-classical (no compatible version released yet)
mathcomp-word (no compatible version released yet)
mathcomp-algebra-tactics (1.2.x not in nixpkgs yet)
mathcomp-real-closed (2.0.0 not in nixpkgs yet)

FWIW @proux01, my suggestion in #173 was to open a PR against this branch rather than testing the update directly in the branch.

Indeed, sorry, I shouldn't have hijacked the current PR.

BTW, the failures should now be down to:

mathcomp-classical, hence mathcomp-analysis and mathcomp-infotheo (no compatible version released yet, planned for January)
mathcomp-word (no compatible version released yet, PR open but didn't heard back yet)


Activity class does not exist

Platform: Android
After npm install react-native-config

Set my env files and setting them in build.gradle:

apply plugin: "com.android.application"

project.ext.envConfigFiles = [
  release: ".env.production",
  debug: ".env.development",
  dps: ".env.dps",
]

apply from: project(":react-native-config").projectDir.getPath() + "/dotenv.gradle"

add resValue under defaultConfig

    defaultConfig {
        ...
        resValue "string", "build_config_package", "com.testenvone"
    }

add dps environment build setting under buildTypes

buildTypes {
        debug {
            signingConfig signingConfigs.debug
        }
        release {
            // Caution! In production, you need to generate your own keystore file.
            // see https://reactnative.dev/docs/signed-apk-android.
            signingConfig signingConfigs.debug
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
        dps {
            initWith debug
            applicationIdSuffix ".dps"
            matchingFallbacks = ['debug']
        }
    }

clean the android project and type command on terminal
npx react-native run-android --variant=dps

It shows BUILD SUCCESSFUL and I can see the app on simulator but can't open it, because has an error about Activity class
BUILD SUCCESSFUL in 5s
46 actionable tasks: 46 executed
info Connecting to the development server...
info Starting the app on "emulator-5554"...
Starting: Intent { cmp=com.testenvone/.MainActivity }
Error type 3
Error: Activity class {com.testenvone/com.testenvone.MainActivity} does not exist.

What step I miss on document ?

I am also facing the same problem

I'm also in this problem

me too

Try changing the directory name of the package's directory (in the path android/app/src/main/java) corresponding to your package ID ( "com.testenvone" ). I tried it and it works fine.

Okay try this:
npx react-native run-android --appIdSuffix dps

Also finding this as an issue for any change in bundle id.

me too

@motogod when running your application. You need to add appIdSuffix to the script and it will pick up the MainActivity
i.e npx react-native run-android --variant=dps --appIdSuffix='dps'


Introducing namerd

Added namerd, a service for managing linkerd (and finagle) name delegation.

:star: yesssssssssssssssssssssssssssssssss!

:star: lgtm


DateTime entry in dashboard is misleading

Is your feature request related to a problem? Please describe.
The DateTime entry in the dashboard is IMHO misleading. As long as there is no down event, it simply shows the date and time the entry was originally added (which is kind of meaningless?) I would have expected it to show the date and time of the last successful check?
Describe the solution you'd like
If there's a reason to keep it the way it is, I'd qualify the DateTime column somehow (i.e. don't call it DateTime but use a different term describing what it really is).
Describe alternatives you've considered
Alternatively, 2 columns might make sense, on for the current DateTime (date and time of the last "event" ?) and a 2nd column for the date and time of the last successful check?
Additional context
Other than that, great piece of software!

I felt this while debugging some issues as well. The row at the top only shows when the first "Down" occurred, but it doesn't give any confidence as to what the status is now. Here are my thoughts on the possible alternatives:

We add a row at the top of the records table, which always display the latest heartbeat time and its status. This will allow us to at least confirm the latest response, when it was checked and what happened.
or,
We change the DateTime field to display a time range if the same event continues for more than 1 heartbeat. If it continues to be down but the message is different, we display a new item. This will be even more informative, but would require quite a bit of re-engineering of the logic of monitor_notification.

@louislam how do you feel about this?

The "DateTime" column describes the time of occurrence. It is how it looks like in UptimeRobot too.
Since the datetime of the last successful check always equals to (DateTime - interval), I prefer to keep one DateTime column only.

but it doesn't give any confidence as to what the status is now.

I agree, but I prefer to implement something similar to UptimeRobot's "Latest downtime". The event list remains untouched.
UptimeRobot screeenshot:

It's clearer in UptimeRobot's UI, they use the term "event" and latest events, this is missing in your UI, hence, the information is IMHO potentially misleading.


DaggerMock on multidex apps

Hi again,
I am trying to apply DaggerMock to espresso UI tests on a multidex-enabled app, and it is giving a ClassDefNotFoundException on the "javax.inspect.Named" class.  By setting up a traditional espresso + dagger testing architecture it is running well. However, we would love to use DaggerMock on this so that we could simplify it much.
Have you tested DaggerMock on multidex-enabled apps ?

Hi, thanks for your report.
No, I haven't tested it yet on a multidex app, fortunately I am not using it in the app I am working on.
And right now DaggerMock is a Java module, it doesn't contains any reference to Android.
Is this a common problem in multidex apps? Do you know if there is a solution to this problems?

Hi,
Yes, multidex-enabled apps must be tested slightly different in UI testing cases.
Concretely, developers must implement a custom multidex-ready test runner to replace the AndroidJUnitRunner on the build.gradle file. Check this: http://developer.android.com/tools/building/multidex.html#testing
Right now I am using a regular dagger configuration and a multidex test runner. However, this requires me to write a lot of code to set up the dependency injection correctly, and that's why I was trying to use DaggerMock. Anyway, really nice tool!

Can you help me to reproduce the error? I created a new branch https://github.com/fabioCollini/DaggerMock/tree/multidex, I added many libs (finally Guava is helpful in an Android example!) and enabled multidex but I don't get any error on Android 6. Am I doing something wrong?

Were there any updates on this issue? I am experiencing the same issue, also on a multidex android app.

I am sorry but I am not able to reproduce the error, I tried on this branch https://github.com/fabioCollini/DaggerMock/tree/multidex but it works. Can you help me to reproduce it? Are you using some different configuration?

It has been a few projects ago since i last worked through multidex testing issues, so i may be slightly off base. As I recall when our test suite was throwing ClassDefNotFound errors it was always from hitting a critical mass of methods, and that particular build has a code path that ended up in the other dex file so could not be instrumented. It would rear its head at some random point in the development cycle, and something as simple as inlining a variable or changing workstations would change the dexed files enough that the tests would pass. Long story short it is hard to reproduce, or write a reliable test to instrument the issue.

I would venture to say the issue is not with the library, and is related to the test runner that the user is running should support multidex applications.

The javax.inspect.Named issue should be related to proguard.
By adding:
-dontwarn dagger.internal.codegen.**
-keepclassmembers,allowobfuscation class * {
   @javax.inject.* *;
   @dagger.* *;
   <init>();
}

-keep class dagger.* { *; }
-keep class javax.inject.* { *; }
-keep class * extends dagger.internal.Binding
-keep class * extends dagger.internal.ModuleAdapter
-keep class * extends dagger.internal.StaticInjection

to proguard-rules.pro the problem should be fixed.


Destroying last brick doesn't always clear level

The bricks remaining counter clearly says 0 (with only non-destructible bricks remaining, or in some cases, no bricks remaining at all) but the detector doesn't move the stage on.
Has only been observed with superball.

The method of counting bricks has been changed and refactored, it looked like there were occasions where non-destructible blocks were occasionally included. Closing for now as currently cannot reproduce.


added touch support to v2.0.0

#24

man this is beautiful!
I would say since this is a feature it should be version 2.1.0 instead of 2.0.1.
If you dont intend to change this I will merge it after your okay.

updated the version to 2.1.0.

Thank you :)

You had a typo in your PR (event instead of e). I wonder how they all can say that it is working ^^

Another qustion: I wonder why you added the event || window.event since we dont need to support IE 8 anymore. Has it something to do with these touch devices?


college domain added @bishwas-py

Lord Buddha Education Foundation college from Kathmandu

@55767 domains/np/edu/lbef/study.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@55767 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Assure that all attributes for ImageWork model are represented in the view

Assure that all attributes for ImageWork model are represented in the view.

attributes...

I think I have all of them.


'Video Unavailable' overlay for certain Youtube channels

When going to watch any videos on the F1 youtube channel I'm getting a 'Video Unavailable' This video contains content from Formula One Management, who has blocked it from display on this website or application message (screenshot below)
This happens on both firefox and chrome on a Mac. When I disable Adblock thing, the video works (with ads).

Script version
5.5 (most recent)
Firefox 126.0
Chrome Version 125.0.6422.142


Tags for AWS Glue Job not working

Description:
When defining tags for AWS Glue Jobs, they are not rendered properly in the rendered CloudFormation Template and hence do not get added to the AWS Glue Job.
Whereas, adding tags for AWS Lambda attaches the tags to the lambda.
Steps to reproduce the issue:

Add Tags to AWS SAM Template for Glue Job.
Run AWS SAM to deploy the job.
Check Glue Job for tags.

Sample AWS SAM Template -
  GlueJob:
    Type: AWS::Glue::Job
    Properties:
      GlueVersion: '1.0'
      MaxCapacity: 5
      Command:
        Name: glueetl
        PythonVersion: '3'
        ScriptLocation: s3://test/hello.py
      DefaultArguments:
        '--extra-jars': 's3://test/jar-with-dependencies.jar'
        '--TempDir': 's3://test/temp'
      Name: my_test_glue
      Description: Glue job created by AWS SAM
      Role: SomeRandomRole
      Tags:
        my_tag_key: my_tag_value
        my_tag_key2: my_tag_value2

Observed result:
Both tags do not show when checking the glue job on the browser or via CLI.
Expected result:
Tags should be added to glue job.

Hi @sahil-gt , thank you for reporting this, but we can't fix this inside of SAM since that is not an AWS::Serverless resource. Could you either open an issue in https://github.com/aws-cloudformation/aws-cloudformation-coverage-roadmap/issues or open an AWS support ticket through your AWS account?


Update gradients_impl.py

Corrected documentation of hessians() function.

Can one of the admins verify this patch?

@tensorflow-jenkins test this please


Various minor cleanups/refactorings to NER infrastructure

Specifically: (1) removed hard-coded BILOU/BIO tags and replaced them with traits BILOU/BIO; (2) cleaned up LoadConll2003 a bit; (3) added some tests to verify that (1) and (2) didn't break anything

This looks good to me, nice cleanup! I'll merge later this evening unless anyone else has complaints.

LGTM


empty string in fields should cause NA

this only seems to affect c().
So c(as_doi("10.1000/1"), "") yields
<digital object identifier[2]>
[1] 10.1000/1 /

yup, same as:
c(biblids::as_doi("10.1000/1"), "foo")

so this isn't an issue with c(), since it affects vec_c() just as well.


Calling StartStreamMatchingAllConditionsAsync() will result in immediate Stop. [<IP_ADDRESS>]

I have set the StoppedStream event to point to my event handler, when i call StartStreamMatchingAllConditionsAsync() the StoppedStream event handler gets triggered, is this an internal problem ? what's going on ?

Hello, which version of Tweetinvi are you using? Can you share your code.
Could you also disable the ExceptionHandler and let me know what error you receive (stack trace if possible).
ExceptionHandler.SwallowWebExceptions = false;

<IP_ADDRESS>, the argument "e" inside the StoppedStream event handler seems to be empty.
private void btnStart_Click(object sender, EventArgs e)
    {
        if (listView1.Items.Count == 0)
        {
            MessageBox.Show("No people to follow, please add atleast 1 name to the follow list.", "Information", MessageBoxButtons.OK, MessageBoxIcon.Information);
            return;
        }

        switch (isStreamRunning)
        {
            case true:
                MessageBox.Show("Streaming is already running!, stop it first before starting it again.", "Information", MessageBoxButtons.OK, MessageBoxIcon.Information);
                break;
            case false:
                ExceptionHandler.SwallowWebExceptions = false;
                filtered_stream.StartStreamMatchingAllConditionsAsync();
                break;
        }
    }

 private void FilteredStreamStoppedHandler(object sender, StreamExceptionEventArgs e)
    {
        tsLabel1.Text = "Inactive";
        isStreamRunning = false;
    }

    private void filteredStreamStreamStarted(object sender, EventArgs e)
    {
        tsLabel1.Text = "Active";
        isStreamRunning = true;
    }

  private void MatchingTweetReceivedHandler(object sender, MatchedTweetReceivedEventArgs args)
    {
        var tweetInfo = args.Tweet;

        using (StreamWriter sw = new StreamWriter(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "debugoutput.txt"), true))
        {
            sw.WriteLine(String.Format("screen_name:{0} Text: {1} IsRetweet: {2} InReplyToStatusIdStr: {3} created_at: {4}",
                tweetInfo.CreatedBy.ScreenName, tweetInfo.Text, tweetInfo.IsRetweet, tweetInfo.InReplyToStatusIdStr, tweetInfo.CreatedAt.ToLocalTime().ToString()));
        }

    }

linvi, did you successfully reproduce the problem ?

No I haven't, is it possible for you to share your project please?
Do you know if the stream works in a Console project. The reason why I ask is the fact that I have another similar issue opened for a WPF app, but the stream works in Console Application.
What I do not understand is that your stream stops but you do not receive any Exception, is it correct?

Yes, correct, i do not get any exceptions.
How can i send you my project privately ?

Please contact me through the codeplex website :
https://www.codeplex.com/site/users/view/linvi, there is a contact link there. Unfortunately Github no longer provide private messaging.

I think this is an internal bug in the latest version, in <IP_ADDRESS> it didn't happen.

Ok thanks for the info. Please share your code it will probably help a lot for debugging this issue.

i'm not going to register a new account on codeplex, i merely hesitated registering an account on here, give me your email.

Could you send it to me here<EMAIL_ADDRESS>Thanks for your help.

Do you have another email ? i failed sending it to that address.

Can you try this one<EMAIL_ADDRESS>

failed to send to that one too.

Can you please go on gitter (with git account) and we will be able to discuss privately.
https://gitter.im/linvi/tweetinvi

Ok, this issue has been resolved, what was done is we passed the creds (TwitterCredentials) directly into the CreateFilteredStream() function.

The issue was that Stream breaking change was not understood when migrating from <IP_ADDRESS> to <IP_ADDRESS>.
Please read the documentation fo <IP_ADDRESS> concerning Stream breaking changes here: https://github.com/linvi/tweetinvi/releases/tag/<IP_ADDRESS>.


Standardize license field in pyproject.toml

What does this PR do?
Standardizing the licenses in integrations pyproject.toml. I first changes the licenses for two random integrations, saw that the CI checks passed, and then made changes to the pyproject.toml files of all integrations.
Motivation
Make the license field consistent across all integrations -- if the new license format passes all CI checks, I can change all of them to a standard version.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

👍 Could you also update the templates we have in ddev here? (for instance this: https://github.com/DataDog/integrations-core/blob/master/datadog_checks_dev/datadog_checks/dev/tooling/templates/integration/check/{check_name}/pyproject.toml#L13)

👍 Could you also update the templates we have in ddev here? (for instance this: https://github.com/DataDog/integrations-core/blob/master/datadog_checks_dev/datadog_checks/dev/tooling/templates/integration/check/{check_name}/pyproject.toml#L13)

Changing these templates causes the CI checks to fail, so I reverted the commit where I tried to update them.


Update ncs to d703cdb7dbc8a7e849805ef2a047ac154918c4f0

This version of NCS contains openthread version: a1816c15640e91019cb4ec1c37ea61129138ad44.

@sunytt Updated the OT reference commit in both PR description nad commit message.


Using a container view controller with FlexibleHeightBar causes issue when the UITableView is mid scroll

I am using a UITabBarController to choose between two UIViewControllers with BLKFlexibleHeightBars and UITableView's. Whenever I switch between the two views, the height of the BLKFlexibleHeightBar can be visible (it is of the background color of the bar).
It only disappears when you scroll away.

I'm not exactly sure what the issue is based on your description, but maybe you can do something in -viewWillAppear which will get called each time you switch tabs. Perhaps something needs to be updated?
If you figure this out or think this is a big with BLKFlexibleHeightBar, let me know. Also, if you have a demo project feel free to post.


Add "Recipients" and "AttachmentNames" properties as part of the output of the cmdlet in the Description area

In the Description area https://docs.microsoft.com/en-us/powershell/module/exchange/get-dlpdetailreport?view=exchange-ps#description, we do not have the "Recipients" and "AttachmentNames" properties mentioned, although they have been added per https://o365exchange.visualstudio.com/IP Engineering/_workitems/edit/1359643.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 54810913-01ba-f2ed-76dd-3d810e4beeda
Version Independent ID: 1fd3a291-d8bd-13b9-785f-8fa88170c1f7
Content: Get-DlpDetailReport (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Get-DlpDetailReport.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

Hi @Alex-Catalin, thank you for your feedback. I'll try to confirm this information as I don't have access to https://o365exchange.visualstudio.com/IP Engineering/_workitems/edit/1359643.
If you have a Microsoft alias, you can link your accounts in GitHub so that a blue "Microsoft submitter" label appears to any PR's or issue you submit. Guidance on it here: https://docs.opensource.microsoft.com/tools/github/index.html
Here is the site you can use to see the mappings between GitHub and Microsoft aliases: https://repos.opensource.microsoft.com/people?q=Alex-Catalin

Hi Dario,
My MS account should be linked to the github account. You gave me these steps before and I followed them to link the 2 accounts 😊.
Thank you,
Alexandru Cazacu
Sr. Support Escalation Engineer
Exchange Online
M365 EMEA Customer Service & Support
alexandru.cazacu<EMAIL_ADDRESS>9 AM - 6 PM (GMT+2)
<EMAIL_ADDRESS>From: Dario Woitasen<EMAIL_ADDRESS>Sent: Tuesday, February 16, 2021 1:16 PM
To: MicrosoftDocs/office-docs-powershell<EMAIL_ADDRESS>Cc: Alexandru Cazacu<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/office-docs-powershell] Add "Recipients" and "AttachmentNames" properties as part of the output of the cmdlet in the Description area (#7212)
Hi @Alex-Catalinhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAlex-Catalin&data=04|01|alexandru.cazacu%40microsoft.com|6c1ce19a2ab64dd3b9c708d8d26c3793|72f988bf86f141af91ab2d7cd011db47|1|0|637490709660190502|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=H9o7CYrWanaKo3vYB7y8jxf2u%2BYGYkP8h2Zdu%2BfJ1r8%3D&reserved=0, thank you for your feedback. I'll try to confirm this information as I don't have access to https://o365exchange.visualstudio.com/IP Engineering/_workitems/edit/1359643https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fo365exchange.visualstudio.com%2FIP%2520Engineering%2F_workitems%2Fedit%2F1359643&data=04|01|alexandru.cazacu%40microsoft.com|6c1ce19a2ab64dd3b9c708d8d26c3793|72f988bf86f141af91ab2d7cd011db47|1|0|637490709660200493|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=jRr780e4ikhzI0jkoZaLVeS%2BRpdOYo%2BOy9ej2FglUPg%3D&reserved=0.
If you have a Microsoft alias, you can link your accounts in GitHub so that a blue "Microsoft submitter" label appears to any PR's or issue you submit. Guidance on it here: https://docs.opensource.microsoft.com/tools/github/index.htmlhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.opensource.microsoft.com%2Ftools%2Fgithub%2Findex.html&data=04|01|alexandru.cazacu%40microsoft.com|6c1ce19a2ab64dd3b9c708d8d26c3793|72f988bf86f141af91ab2d7cd011db47|1|0|637490709660200493|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=phtpuz11vn65H5nScw73OqEYW26Awp7IM4mOVX%2BUhf8%3D&reserved=0
Here is the site you can use to see the mappings between GitHub and Microsoft aliases: https://repos.opensource.microsoft.com/people?q=Alex-Catalinhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepos.opensource.microsoft.com%2Fpeople%3Fq%3DAlex-Catalin&data=04|01|alexandru.cazacu%40microsoft.com|6c1ce19a2ab64dd3b9c708d8d26c3793|72f988bf86f141af91ab2d7cd011db47|1|0|637490709660210489|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=QCmxdXzB25d%2FsADjQx%2Bc6vIX7atTnzlOGYb8F8RpH8k%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F7212%23issuecomment-779769198&data=04|01|alexandru.cazacu%40microsoft.com|6c1ce19a2ab64dd3b9c708d8d26c3793|72f988bf86f141af91ab2d7cd011db47|1|0|637490709660210489|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2BAF2bAgVPfr0pduFycvFzezOz%2Braxnm9J4C%2BIxpZHx0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKGDFI57U7NBOGJVTEDJWJLS7JHWLANCNFSM4XCO53BQ&data=04|01|alexandru.cazacu%40microsoft.com|6c1ce19a2ab64dd3b9c708d8d26c3793|72f988bf86f141af91ab2d7cd011db47|1|0|637490709660220481|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=vKEFkLIuBoWHCuZrNnIK1FYPvMmPNmsSWIvmsuHogt8%3D&reserved=0.


Download JSON Doesn't Work

Location
https://test.swarm.city/make-backup-profile/
Expected behavior
Click "Download my file" button and the app will automatically download the JSON to the phone.
Actual behavior
After clicking "Download my file" button, the screen changes to https://test.swarm.city/download-success-profile/, but download doesn't happen.
Steps to reproduce the problem
Go to https://test.swarm.city/make-backup-profile/.
Click "Download my file" button.
Operating system / hardware
Moto G6 Play, Android 8.0.0, Chrome v. 69.0.3497.100

On my Android using Chrome... uninstalling the latest chrome update triggers the download to work a couple times. Then it stops working again when I update the browser. If I install the update again download backup works again as expected.

I tried the same thing as Jenn and it didn't work for me. Uninstalled Chrome and reinstalled.

@matthewcarano  I cant recreate this on browser stack and I don't have a physical Android device, maybe we can schedule some time together to debug this one


starnge new point!

I've been at this for hours, I watched your all your demo videos on youtube and some other video, and for the love of god I couldn't figure out what is wrong. I keep finding a new point on the shape and it seems I can't arrange the points as I want. please find the video and the SVG file below

Archive.zip

I tried with the play pause button as well, I just want to define which point 1,2,3,4 on the top half of the triangle and the first square in pause why can't I just do that? I already separated triangle with on additional point in the source svg itself , why is it so unintuitive to assign a number to point. going crazy here :(

I've learned couples of things, don't know if it's true
1.it's always better to shapeshift from lesser point vector to bigger one
2.we need to aware of how animation ended before we even do it and plot our course like in your example instead of using pause directly you rotated it which made animation lot smother lot quicker.
3.should be aware of all properties and know when to use them. translation, pivot, rotation scale, alpha etc. just start and end states of animation in SVG is not enough like other animation software.
but I still trying to figure out why some time number changes on hover, and how to control points when there is 3 of them at the same place? how to select the middle one?

finally getting what I want but circling back to my original question. the half of the split mic has 4 points and the first square of the pause has 4 points and same for the other half and yet the auto adds the fifth point for first half couldn't understand why?

also, I got the animation I want on the bottom right corner (like corner radius is reducing to 0) but I couldn't reproduce it anywhere else also I'm not sure how it happened please check the gif and attached file
mic_pause.shapeshifter.zip


[v2.6] Repatriate from v2.5

This PR merges release/v2.5 in to master.

Closing because we have removed the repatriation process from development workflow. See the DEVELOPING.md in the master branch for details. I have reviewed the commits above and these were all backports from master and do not need to be repatriated.

Closing because we have removed the repatriation process from development workflow. See the DEVELOPING.md in the master branch for details. I have reviewed the commits above and these were all backports from master and do not need to be repatriated.


Fix an incorrect field name in FlowGraphLayoutRequest._complete

FlowGraphLayoutRequest.on_complete was incorrectly referenced as _on_complete in FlowGraphLayoutRequest._complete. This simple PR fixes the issue.

Thanks!


Not able to use the plugin to get objects from cross account s3 access grant - getting GetObject access denied

Steps Taken:
Cross-Account S3 Access Grant Setup:
I used the s3 controltower get_access_data API to verify the cross-account setup, and it confirmed that the access grant is functioning correctly. Below is the code I used:
response = client.get_data_access(     AccountId='xxx',     Target='s3:xx',     Permission='READ' )
Attempt to Access S3 Objects via Studio Notebooks:
From the cross account, I installed and registered the required plugin, then attempted to retrieve objects from S3 (s3 grant from account A) using the get_object API. Here’s the code I executed:
`import botocore.session
from aws_s3_access_grants_boto3_plugin.s3_access_grants_plugin import S3AccessGrantsPlugin
import boto3
import logging
session = boto3.Session()
s3_client = session.client('s3', region_name='eu-west-1')
plugin = S3AccessGrantsPlugin(s3_client, fallback_enabled=False)
plugin.register()
s3_client.get_object(Bucket='s3-xxx', Key='data/xx')
`
However, I encountered the following error: ClientError: An error occurred (AccessDenied) when calling the GetObject operation: Access Denied.

Hi aswin2025,
Thank you for bringing this to our attention. We were able to reproduce the issue, and it was a bug. This should be patched as of release 1.1.0. Can you please upgrade and confirm your problem is resolved?


[REQUEST] macOS support

It is planned, almost there

Mac OS support added in the development branch (not all features ported, but it is possible to compile and run C# smart contracts)


Failed to detect a provider for FreeBSD 10.2

Hi! In the consul cookbook we have a "poise_service" resource failure on FreeBSD due to ProviderNotFound exception. Is it supported in "poise_service" ? Is there a way to work it around?
         * consul_service[consul] action enable
           * directory[/var/lib/consul] action create (up to date)
           * poise_service[consul] action enable

             ================================================================================
             Error executing action `enable` on resource 'poise_service[consul]'
             ================================================================================

             Chef::Exceptions::ProviderNotFound
             ----------------------------------
             Cannot find a provider for poise_service[consul] on freebsd version 10.2-RELEASE-p7

             Cookbook Trace:
             ---------------
             /tmp/kitchen/cache/cookbooks/poise-service/files/halite_gem/poise_service/service_mixin.rb:89:in `block in action_enable'
             /tmp/kitchen/cache/cookbooks/poise-service/files/halite_gem/poise_service/service_mixin.rb:154:in `notify_if_service'
             /tmp/kitchen/cache/cookbooks/poise-service/files/halite_gem/poise_service/service_mixin.rb:88:in `action_enable'
             /tmp/kitchen/cache/cookbooks/consul/libraries/consul_service.rb:80:in `action_enable'

             Resource Declaration:
             ---------------------
             # In /tmp/kitchen/cache/cookbooks/consul/recipes/default.rb

       53: consul_service service_name do |r|
       54:   version node['consul']['version']
       55:   config_file config.path
       56:   program install.consul_program
       57:
       58:   unless windows?
       59:     user node['consul']['service_user']
       60:     group node['consul']['service_group']
       61:   end
       62:   if node['consul']['service']

             Compiled Resource:
             ------------------
             # Declared in /tmp/kitchen/cache/cookbooks/consul/recipes/default.rb:53:in `from_file'

             poise_service("consul") do
        action [:enable]
        retries 0
        retry_delay 2
        default_guard_interpreter :default
        service_name "consul"
        command "/opt/consul/0.7.1/consul agent -config-file=/etc/consul/consul.json -config-dir=/etc/consul/conf.d"
        directory "/var/lib/consul"
        user "consul"
        environment {"GOMAXPROCS"=>"2", "PATH"=>"/usr/local/bin:/usr/bin:/bin"}
        options_systemd {"template"=>"consul:systemd.service.erb"}
        options_sysvinit {"template"=>"consul:sysvinit.service.erb"}
        options_upstart {"template"=>"consul:upstart.service.erb", "executable"=>"/opt/consul/0.7.1/consul"}
             end

             Platform:
             ---------
             x86_64-freebsd10.2

Thanks!

I don't have a provider for FreeBSD but the design is such that you could write one in your own cookbook. If it's simple enough to not need any external dependencies I would be happy to include it in poise-service, but I'm going to close that as I don't plan to write one myself due to a lack of knowledge of BSD internals. Check out things like poise-service-runit and poise-monit for examples of writing providers as plugins.


Cannot run code after :IPython command.

Hello,
I struggled to get this installed and working, did have issues with the IPython command at first. But updating remote plugins worked for me.
Now i have the issue that i can make an IPython window but i can use F5 to send code to it and run any code. The Error message that i have:
Error detected while processing function IPyRun[1]..remote#define#notify:
E475: Invalid argumanet: Channel doesn't exist
Screenshot is posted.
I am using windows and Lazy to install this plugin. I have also shown how i have installed the plugin and the others i have installed. (There is nothing in the nvim-ipy.lua file under plugin_config btw, it is all commented out.)
If you have any advice to get code running in the ipython console i would really appreciate it.
Please just ask me if you need any more info about anything, dont know if i provided enough here.

did you solve this?

did you solve this?

i did not, i just use toggle term now and launch ipython through that. if you look on my github i have my neovim conf with a send to terminal setup here


differences with redux dev-tools?

sorry for non-tech issue, but it might improve your install funnel if you could be clear about the differences vs. redux devtools, which a lot of people use already?
at first glance they look pretty similar, time-travel debugging etc.
https://github.com/zalmoxisus/redux-devtools-extension

and they have various fancy features like state 'chart'
also why does this require an NPM package to be installed, as opposed to just working as a chrome extension?

Hi @dcsan , great question. Reactime is targeted towards React-only (think components using this.state or hooks) projects, whereas Redux DevTools is meant for those that use Redux for state management. With that said, we are essentially inspired by them as the primary goal of this tool is to bring time traveling over to React. In order to do that as a third-party tool, however, we would need direct access to the component tree of user's application. Hope that's helpful!

thanks for the reply. If I am using redux, does this tool give any extra insights? there is still a level of detail missing in terms of the order of when selectors get updated but that's deep into redux land I guess.
good luck with it and thanks for open-sourcing!


IZPACK-1688: Update PR #704

This PR contains the changes from PR #704 and requested changes.

LGTM for now. In order to be future prove we need to eliminate or change com.izforge.izpack.test.util.ClassUtils in the future though.


feat(pixels): add my new pixel (24, 44)

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Following the TwilioQuest I've added my new pixel and I need to merge my pull request to proceed.
Thanks !!


Please add Azure Red Hat Open Shift to the list of supported services.

The list of supported services is missing Azure Red Hat Open Shift. This was GA'ed according to this feature https://github.com/Azure/OpenShift/issues/238 and is already in the Azure Red Hat OpenShift documentation.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 985eab9b-60f7-480a-c649-1fd7c6105646
Version Independent ID: 4d5bbc09-fa5a-c67e-b4b8-75a5229506c0
Content: Customer Lockbox for Microsoft Azure
Content Source: articles/security/fundamentals/customer-lockbox-overview.md
Service: information-protection
Sub-service: aiplabels
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@francislacroix
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Azure Red Hat OpenShift has been added.  We sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close