How to approach identifier provenance

Separating the question of identifier provenance from #347:
Initiating comment by @schristley is here:
https://github.com/airr-community/airr-standards/issues/347#issuecomment-1018745723

@schristley seems content to implement custom Rearrangement fields (non-schema fields) to track original identifiers in VDJServer.
@bcorrie wants a mechanism to preserve original identifier fields uploaded by users into the ADC.
@javh thinks provenance should go in a provenance object.

Fight!!!

My main point here (https://github.com/airr-community/airr-standards/issues/347#issuecomment-1047211943) is that as a data curator, I need to preserve information in my repository so that I can figure out why my rearrangements/clones/cells that are loaded are looking suspicious. When things seem odd in my repository, I need to be able to figure out why. If I lose the information from the annotation tool that links info together in a specific analysis (such as cell_id ) and how things are linked in the original data files I am in trouble.
Personally, I think if we do this as custom fields I think we are NOT doing the data curator any favors - everyone then does it differently or perhaps doesn't do it at all (because they don't know they should).
I think the standard should make provenance like this simple.
I am intrigued as to what a provenance object would look like and how it might help - thoughts?

@bcorrie For my clarification, are you only referring to ID fields that conflict with AIRR id fields? Or are you also talking about additional non-AIRR id fields that tools might assign (e.g., clonotype_id for 10x)? And/or are you also talking about custom non-id fields that don't map to AIRR (e.g., is_cell for 10x)?

@javh thinks provenance should go in a provenance object.

A provenance object is an interesting idea; essentially formalizing the custom approach. A simple solution may be a mapping table between identifiers. However, before we go along that path, what's the scope? Will it be a defined AIRR object, will there be an ADC endpoint to query and download? If it's purely a private/internal table for a data repository, then I don't see spending AIRR-C resources on defining. Or do we consider this fundamental AIRR provenance?

Fight!!!

Rule 1 of Fight Club is don't talk about Fight Club! ;-D

@bcorrie For my clarification, are you only referring to ID fields that conflict with AIRR id fields? Or are you also talking about additional non-AIRR id fields that tools might assign (e.g., clonotype_id for 10x)? And/or are you also talking about custom non-id fields that don't map to AIRR (e.g., is_cell for 10x)?

All, none, both... 8-)
I am pointing out that there is a tension between information that annotation tools generate (e.g. identifiers for specific cells and clones) and the AIRR Standards definition of fields that play the same or similar roles (e.g. identifiers for specific cells and clones).
Lets face it, the AIRR Standard's fields for something like an identifier for a specific cell (cell_id) are driven by the use of the same concept by the annotation tools.  The reason the AIRR Standard has them is because they are conceptually needed - and that is the same reason the annotation tools produce them. So I don't think it correct to say that _id fields from an annotation tool like cellranger's cell_id "conflict" with the AIRR cell_id field. They are capturing the same concept.

A simple solution may be a mapping table between identifiers.

As far as I am concerned, at least at a very simple level, all the AIRR Standard is is a giant mapping of fields - and "we've already got one..." - https://www.youtube.com/watch?v=Ea8GyscSFaQ
https://github.com/sfu-ireceptor/config
Consider cell_id from 10X as an example use case - do we mean:

AIRR cell_id == 10x cell_id
AIRR cell_id == new uniqueID(), 10x cell_id > /dev/null
AIRR cell_id == new uniqueID(), AIRR custom cell_id_annotation_tool = 10X cell_id
AIRR cell_uid == new uniqueID(), AIRR cell_id = 10X cell_id

I like the last one the best - with a nominal mapping of an annotation tools concept of a ID for a Cell == cell_id and the notion of an ADC concept that has unique/PID constraints being an ID by itself.
I get sad when I see data generated by a tool being marked, by the AIRR Standard no less, as not useful and being sent to /dev/null. It just seems like a bad idea... 8-)

AIRR cell_id == 10x cell_id
AIRR cell_id == new uniqueID(), 10x cell_id > /dev/null
AIRR cell_id == new uniqueID(), AIRR custom cell_id_annotation_tool = 10X cell_id
AIRR cell_uid == new uniqueID(), AIRR cell_id = 10X cell_id

None of the above, I like:

AIRR cell_id, 10x cellular_id for linking to external 10x files

The fields are independent, so no conflict. AIRR cell_id follows all of the AIRR (and ADC) requirements, while 10x has a custom field for linking to non-AIRR external 10x files.

Fight!!!

I am pointing out that there is a tension between information that annotation tools generate (e.g. identifiers for specific cells and clones)

AN _id IS NOT INFORMATION! AN _id IS NOT INFORMATION! AN _id IS NOT INFORMATION!
😂😂😂
More seriously, I am very much against

AIRR cell_uid == new uniqueID(), AIRR cell_id = 10X cell_id

for the reasons discussed ad nauseum in the other threads. Beyond that, I care relatively little whether the original cell_id gets discarded, goes in a custom field, goes in a new AIRR-reserved field, or goes in a new AIRR-defined Provenance object. I think @schristley is right that

If it's purely a private/internal table for a data repository, then I don't see spending AIRR-C resources on defining.

But I guess I don't see the harm in ratifying whatever @bcorrie is already using for this anyway 😉

Hrm. I think attributing inherent value, that should be preserved, to user data is a distraction.  VDJServer and the iReceptor gateway are also tools. Cellranger munges input fastq data, iReceptor munges input AIRR data... it's the circle of life.
I like this comment by @bcorrie:

I need to preserve information in my repository so that I can figure out why my rearrangements/clones/cells that are loaded are looking suspicious. When things seem odd in my repository, I need to be able to figure out why.

This is something meaty to chew on.  I read this need as a changelog - not denoting input data as immutable. I don't know what a provenance object would look like. I think we need to nail down the use case, scope, etc. But, maybe something like:
Provenance:
    properties:
        sequence_id:
            type: string
            description: sequence_id of the current record.
        data_processing_ids:
            type: array
            description: List of data_processing_id values associated with each historical change.
        sequence_provenance:
            type: array
            description: List of historical sequence_id values.
        cell_provenance:
            type: array
            description: List of historical cell_id values.

Where all arrays are required to be equal length.
Would something along these lines answer the "something went wrong, why?" question?

@scharch Yeah, good point. I think that's covered by DataProcessing:data_processing_files.
Personally, I'd approach this problem using a human readable log output by whatever loads the data, but... I'm not opposed to trying to formalize this for the ADC context.

Responding to @bcorrie from https://github.com/airr-community/airr-standards/issues/347#issuecomment-1048056738:

So when I process some 10X studies (N samples from one study and M samples from another study) generating AIRR compliant files in preparation for analysis, I replace the source 10X cell_id with a unique AIRR cell_id to make sure cell_id is unique across my analysis of interest.
Now I want to confirm that the data I just processed for a certain 10X cell_id (TACGGATGTACACCGC-1) from a single subject in my source data is correct across the data I am going to use for my analysis. I can't...
Similarly, if I want to look at an AIRR unique cell_id in my processed data and then find the source information in the original 10X produced data files. Again, I can't...
So we have broken the link between the data in the AIRR compliant files to the original source data - data/"information" can no longer be mapped between the two...
Now if you truly trust the tools that do all of that processing, then maybe you don't want to do any provenance or reproducibility checks... But that is not how I would do things 8-)
Here is an example of what you get from a repository with our current implementation. If I maintain the annotation tool cell_id in some form, I can cross check the validity of the data I loaded with the original 10X files. If I don't, I can't... If you are a data steward maintaining an ADC repository, this is an important step...
Basically I want to be able to ensure that cell_id_annotation_tool = TACGGATGTACACCGC-1 links the correct data in the original 10X files (ERS1-TRA.tsv, ERS1-vdj_t_gex.json, ERS1-vdj_t-cells.json) that I as the data curator have maintained...

I think you are making the point for me that this is an inherently local function. No matter how we implement cell_id_annotation_tool, you will always need access to "the original 10X files (ERS1-TRA.tsv, ERS1-vdj_t_gex.json, ERS1-vdj_t-cells.json)." So immediately we've ruled out this being a useful field for anything I download from the ADC (or even get from a collaborator, frankly).
I'm not ruling out adding Provenance to the schema for local use. But we've never really figured out how we want to include/describe links between files (as opposed to data) in the schema. What if the path becomes stale? How do you ensure that the original data hasn't gotten corrupted? We could of course decide to ignore these issues and just report the links, but it certainly limits the applicability of your use case.
And then we still have to circle back to @schristley's point, which is that since the AIRR schema is designed to foster data sharing, how appropriate/useful is it to spend effort on what would be an inherently local/private schema object? I think there's a good case to be made that it can/should be included under the reproducibility part of the rubric, even if not the sharing part, but it's far from a forgone conclusion...

I need to preserve information in my repository so that I can figure out why my rearrangements/clones/cells that are loaded are looking suspicious. When things seem odd in my repository, I need to be able to figure out why.

This is something meaty to chew on. I read this need as a changelog - not denoting input data as immutable. I don't know what a provenance object would look like. I think we need to nail down the use case, scope, etc. But, maybe something like:

I would include in an object that records the actual change. In IT systems, these are sometimes called audit tables, i.e., recording when a data field is changed so you can audit those changes at a later time. Our use might be more specific so the structure might be simpler.
Audit:
  properties:
    field_name:
      type: string
      description: field that was changed
    old_value:
      type: string
      description: old value for field
    new_value:
      type: string
      description: new value for field
    data_type:
      type: string
      description: data type of field
      enum:
        - string
        - number

Then you record a list of these objects. You could also add a date-time for when the changed occurred and a username who did the change, but not sure if we need those.
Now a basic script can walk through each data record, and for each field_name change new_value back to old_value, and save the data. That should give you the "original" file contents.
Now you need to define a scope that these changes apply to. This can be done in various ways. One way is if you want all of these audit records to be in a single table, then you need to additional fields (foreign keys) that specify what data record was changed. Another approach is there is a an audit table for each object type like repertoire_audit, rearrangement_audit and so on. That then implicitly defines the scope for the changes.
I don't think file names and data processing are needed. If we stick to the limited scenario where _id values are changed when data is loaded into ADC, then "reversion" is downloading the data from the ADC and rewriting the _id fields with their old values. You can put data in whatever file you want.

This is something meaty to chew on. I read this need as a changelog - not denoting input data as immutable. I don't know what a provenance object would look like. I think we need to nail down the use case, scope, etc. But, maybe something like:

Use case: http://www.ireceptor.org/repositories/provenance

And a provenance use case moving between versions of an AIRR Standard release:
http://ireceptor.irmacs.sfu.ca/repositories/v3-0

This is not new, but please don't take away fields that we need for provenance and reproducibility...

I think you are making the point for me that this is an inherently local function. No matter how we implement cell_id_annotation_tool, you will always need access to "the original 10X files (ERS1-TRA.tsv, ERS1-vdj_t_gex.json, ERS1-vdj_t-cells.json)." So immediately we've ruled out this being a useful field for anything I download from the ADC (or even get from a collaborator, frankly).

That is the whole point - this isn't meant to be useful to you as a consumer of my data, it is meant to be useful to me as a curator so I can make sure the data you reuse is accurate...
It is a mistake to look at the AIRR Standard from just the perspective of someone who uses the data. If you don't want to use this field, then don't use it, but don't prevent others (a data curator) from having the ability of use the field if there is a use case for it!

If you don't want to use this field, then don't use it, but don't prevent others (a data curator) from having the ability to use the field if there is a use case for it!

No one has suggested preventing you from using the field, the question is whether or not to design and implement it as part of the AIRR schema.
Since there is general openness to the idea, my questions are:

Would a Provenance or Audit object make sense without explicitly linking to/encapsulating the original data files?
If not, are we able to preserve (enough of) that linkage to make the cost/benefit of adding one to the schema worthwhile?

My own sense is that the answers to both are negative, but it's your use case, so I guess you tell me. But again, even if I am correct and we don't implement this as part of the schema, it doesn't stop you from doing it on your own in whatever way works best for you...

No one has suggested preventing you from using the field, the question is whether or not to design and implement it as part of the AIRR schema.

If there is a use case from the AIRR Community for it (e.g. those that curate data for reuse), then it should be part of the standard... If it isn't part of the standard then it is next to useless for the AIRR Community...

@bcorrie reserving my remaining philosophical disagreements, please answer my questions so we can get to work

If there is a use case from the AIRR Community for it (e.g. those that curate data for reuse), then it should be part of the standard... If it isn't part of the standard then it is next to useless for the AIRR Community...

The use case should be generally applicable though. We don't, as a pseudo-rule, define fields/objects for use cases specific to 1-2 tools. We encourage custom fields in that case. Though, we've usually made exception for the ADC or things that are really obviously necessary.
So... I think if we should focus on finding a solution that covers the needs of VDJServer and iReceptor specifically, under the assumption that it'll be applicable to the ADC as a whole, then that should be good enough.

I don't think file names and data processing are needed. If we stick to the limited scenario where _id values are changed when data is loaded into ADC, then "reversion" is downloading the data from the ADC and rewriting the _id fields with their old values. You can put data in whatever file you want.

I rather like the json audit table... It seems like @bcorrie wants the data file links though. What about input and output references to files / records in the ADC? In the spirit of WDL task definitions:
https://github.com/openwdl/wdl/blob/main/versions/1.0/SPEC.md#task-definition

The use case should be generally applicable though. We don't, as a pseudo-rule, define fields/objects for use cases specific to 1-2 tools. We encourage custom fields in that case. Though, we've usually made exception for the ADC or things that are really obviously necessary.

Are there any single-cell tools that don't have a cell_id concept as a link between files/objects in its internal data model? So I  would argue it isn't specific to 1-2 tools, it is specific to the concept of a Cell and how single cell tools process such data.

So... I think if we should focus on finding a solution that covers the needs of VDJServer and iReceptor specifically, under the assumption that it'll be applicable to the ADC as a whole, then that should be good enough.

As I say, this argument isn't specific to the ADC. It applies to files on disk as well. If you transform data from the 10X file format for two samples into AIRR repertoire, rearrangement, clone, and cell files for processing by an AIRR compliant tool (replacing the 10X cell_id with a unique ID), would you be able to tell me if the data in the AIRR files are a correct transformation of the source data in the 10X files? I don't think you can. If not, you have a non-reproducible data transformation.

Since there is general openness to the idea, my questions are:

Would a Provenance or Audit object make sense without explicitly linking to/encapsulating the original data files?

I can't answer that question, I don't know what these are or what the look like. I do know that the main reasons for our sequence_file and data_processing_files are for provenance and reproducibility - so to date we have been unable to provide these features without linking to files.

If not, are we able to preserve (enough of) that linkage to make the cost/benefit of adding one to the schema worthwhile?

I am not sure what you are asking here. What linkage are we preserving and what costs/benefits are we talking about...

Are there any single-cell tools that don't have a cell_id concept as a link between files/objects in its internal data model? So I would argue it isn't specific to 1-2 tools, it is specific to the concept of a Cell and how single cell tools process such data.

The need to preserve original identifiers is what is tool-specific. Modifying the cell identifiers is common and I can't think of a single-cell tool that cares about tracking the changes to cell_id they may have made. If you want reproducibility, then you provide it via code describing the steps and tool version numbers, not via some sort of schema-defined diff on the files.
I don't see this being applicable outside VDJServer and iReceptor. At least, initially. Which is perfectly fine. It'll give us a clear picture of the problem that needs to be solved.

@bcorrie wants a mechanism to preserve original identifier fields uploaded by users into the ADC.

Just to be clear about @javh 's initial statement. I DO NOT want a mechanism to preserver original fields uploaded by users into the ADC. I DO WANT to preserve fields that we think are important to the use cases we have in the AIRR Community by making them part of the AIRR Standard.

Again, to be clear, in regards to this issue, I don't want provenance on individual AIRR fields (to be able to track changes to fields). I want to be able to have data provenance and reproducibility on data that is converted from common tool chains (e.g. 10X) into the AIRR Standard data formats for repertoires, rearrangements, clones, and cells.
In my opinion the AIRR Standard should facilitate this, not hinder it.

@bcorrie, All right, I think we need a more precise definition of your problem then.
How is what you want not accomplished via, say, providing a WDL file for conversion steps? Or maintaining a copy of the files the user original uploaded? How is the AIRR Standard even relevant to this problem?

Again, to be clear, in regards to this issue, I don't want provenance on individual AIRR fields (to be able to track changes to fields). I want to be able to have data provenance and reproducibility on data that is converted from common tool chains (e.g. 10X) into the AIRR Standard data formats for repertoires, rearrangements, clones, and cells.
In my opinion the AIRR Standard should facilitate this, not hinder it.

@bcorrie Expanding this to a broader context makes it sound like #313 , if this is your intent then I don't think we need a separate duplicate issue. Close this issue and use the original one. You already have a team working on reproducibility so you should be able to provide specific suggestions on how the AIRR Standards should be updated. Maybe the preliminary data processing design is sound, and you just need to start specifying it in more detail.
If somehow you mean something independent from data processing reproducibility then you need to clearly state how this issue is different, and update the issue title and main comment to reflect that.

If somehow you mean something independent from data processing reproducibility then you need to clearly state how this issue is different, and update the issue title and main comment to reflect that.

I didn't create this issue... 8-)

All I want is a cell_id and a cell_uid or cell_pid

All I want is a cell_id (as per the tool definition) and a cell_uid or cell_pid (that can be used broadly and changed at will)

These are just arbitrary names, what if we call them cell_ref (as per the tool definition) and cell_id (the AIRR identifier)?

All I want is a cell_id (as per the tool definition) and a cell_uid or cell_pid (that can be used broadly and changed at will)

These are just arbitrary names, what if we call them cell_ref (as per the tool definition) and cell_id (the AIRR identifier)?

I believe that would work - as long as they are both part of the AIRR standard and cell_ref isn't a "custom" field.

I believe that would work - as long as they are both part of the AIRR standard and cell_ref isn't a "custom" field.

Why can't it be a custom field? cell_ref would just be a comment then, with no meaning absent the raw files. Seems very custom to me.
Let's take a concrete example:

Two sets of FASTQ files, one per sample, processed with cellranger.
Data loaded into R using the standard BioC tools.
Custom downstream analysis.

cell_id has the following edits:

FASTQ ~ ATGC. Same value observed in both sample A and B. Sample A has multiple instances of ATGC.
cellranger output ~ ATGC-1. Same value observed in both sample A and B. Sample A also has ATGC-2.
DropletUtils::read10xCounts ~ 2-ATGC-1 and 2-ATGC-2 in sample A, 1-ATGC-1 in sample B. User didn't specify 2- = A, but you figured it out somehow.
Some downstream tool (I'm looking at you scVI), reassigned the cell identifiers to 2-ATGC-1 -> 1,  2-ATGC-2 -> 400, 1-ATGC-1 -> 20.

None are globally unique. User uploaded (4). How is cell_ref = {1, 400, 20} valuable?

All I want is a cell_id (as per the tool definition) and a cell_uid or cell_pid (that can be used broadly and changed at will)

These are just arbitrary names, what if we call them cell_ref (as per the tool definition) and cell_id (the AIRR identifier)?

I believe that would work - as long as they are both part of the AIRR standard and cell_ref isn't a "custom" field.

To be more precise, cell_id is the AIRR identifier field for linking AIRR objects in the AIRR Data Model. It should be unique in the local file context and will be overwritten with a globally unique and persistent identifier when the data is loaded into the ADC.
We need a better name than cell_ref, maybe tool_cell_id, it is assigned the original value of cell_id assigned by the tool when the data is loaded into the ADC. Anybody that downloads data from the ADC can either use tool_cell_id directly, or they can copy tool_cell_id to cell_id in the data to "reproduce" the original tool file.
This is the same solution I presented earlier, I just suggested *_original_id names, but really we can call them anything.

Instead, they can specified as rearrangement extensions for the ADC API.

Seems fine to me as long as cell_id stores the gid/pid and doesn't get redefined to be the "original" identifier (whatever "original" means).
Though, I like your audit table idea better. It's really the same thing though. Just in a fit-to-purpose object instead of Rearrangement.

Though, I like your audit table idea better. It's really the same thing. Just in a fit-to-purpose object instead of Rearrangement.

Me too in the sense that it's general and could be integrated throughout data processing. This other solution is really just a specific hack and doesn't handle the complexities that you point out in your example, but I feel Brian is fixated on just his one use case, 10x cells, and he hasn't thought through the larger context, i.e., what about clones, what about tools that generate their own repertoire_id and/or repertoire_group_id and so on. So we take this as an initial solution, but as the context becomes greater, it might evolve into something like our original ideas.

To be more precise, cell_id is the AIRR identifier field for linking AIRR objects in the AIRR Data Model. It should be unique in the local file context and will be overwritten with a globally unique and persistent identifier when the data is loaded into the ADC.

I want to emphasize that there is a strong coalition around this point: @bussec @javh @scharch and @schristley have all said/agreed with some version of it.

Anybody that downloads data from the ADC can either use tool_cell_id directly, or they can copy tool_cell_id to cell_id in the data to "reproduce" the original tool file.

The above-named also all seem to be onboard with this, possibly with varying degrees of reluctance/eye-rolling about a reserved field vs a custom one. The problem seems to be that @bcorrie (correct me if I'm wrong) is unhappy with the prospect of this copy/overwrite operation and wants cell_id to always and only reflect the pseudorandom string generated by the most recent (per @javh) processing tool to touch the data before upload to the ADC.
But unless I'm wrong about that math, I think we're all pretty clear on where we all stand and we don't need to continue rehearsing the same arguments...

To be more precise, cell_id is the AIRR identifier field for linking AIRR objects in the AIRR Data Model. It should be unique in the local file context and will be overwritten with a globally unique and persistent identifier when the data is loaded into the ADC.

I want to emphasize that there is a strong coalition around this point: @bussec @javh @scharch and @schristley have all said/agreed with some version of it.

@bcorrie agrees as well - and has never stated such a field was not needed. We need an identifier at the AIRR Standard level that is unique in the context that it is being considered (local file, etc) and is controlled (i.e. can be over written) by the tools using it within that context. The ADC will use it in exactly the same way (in the ADC context), with the uniqueness and persistence criteria of the identifier in the ADC yet to be finalized.

The above-named also all seem to be onboard with this, possibly with varying degrees of reluctance/eye-rolling about a reserved field vs a custom one. The problem seems to be that @bcorrie (correct me if I'm wrong) is unhappy with the prospect of this copy/overwrite operation and wants cell_id to always and only reflect the pseudorandom string generated by the most recent (per @javh) processing tool to touch the data before upload to the ADC.

What @bcorrie has been saying for some time is that we also need the equivalent of tool_cell_id, which has a uniqueness criteria within the DataProcessing context that it was created. That is, it is the ID of the Cell object as defined by the tool described in the DataProcessing. IMNSHO this is critical to data curation, data provenance, and reproducibility. I would prefer that this be in the AIRR Standard, but I am OK with it being an ADC API extension if others insist that it is not "AIRR Standard worthy" (with the appropriate reluctance, eye roll, and heavy sigh). It looks like @schristley and I agree that this is probably OK so we can move forward with that...

Me too in the sense that it's general and could be integrated throughout data processing. This other solution is really just a specific hack and doesn't handle the complexities that you point out in your example, but I feel Brian is fixated on just his one use case, 10x cells, and he hasn't thought through the larger context, i.e., what about clones, what about tools that generate their own repertoire_id and/or repertoire_group_id and so on.

Your kidding - right? (eye roll)
Has anyone in this group actually tried to create an AIRR cell.json file? An AIRR clone.json file? An AIRR GEX.json file? Perhaps tried to generate some experience generating such AIRR compliant files based on a common tool chain?
https://github.com/sfu-ireceptor/dataloading-curation/tree/master/test/10x/HC1 (sorry, no GEX, they are too big)
Does anyone's tool use them as input (is anyone working on AIRR compliance for these files in their analysis tools)?
Perhaps reading AIRR cell and GEX JSON files: https://github.com/sfu-ireceptor/dataloading-mongo/pull/50
Or maybe AIRR Clone JSON files: https://github.com/sfu-ireceptor/dataloading-mongo/pull/51
Does anyone have a repository that actually stores all of this data in an AIRR compliant format (http://single-cell.ireceptor.org/) that implements the /clone (curl -d '{"size":1}' http://single-cell.ireceptor.org/airr/v1/clone), /cell (curl -d '{"size":1}' http://single-cell.ireceptor.org/airr/v1/cell), and /expression (curl -d '{"size":1}' http://single-cell.ireceptor.org/airr/v1/expression) endpoints
Perhaps you want to download and try out a repository with all these features - careful as it is on the bleeding edge of the ADC: https://github.com/sfu-ireceptor/turnkey-service-php/tree/master
Or perhaps you might be excited about a user interface that explores the AIRR Data Commons using these new ADC features, allowing users to explore ADC repositories that have any or all of Rearrangement, Clone, or Cell/GEX data

Or maybe a user interface that is integrated analysis tools that compute on and analyze data sets downloaded from the AIRR Data Commons: https://github.com/sfu-ireceptor/gateway/tree/analysis
Right, we are only fixated on this one use case... 8-)

Phew, I feel much better now... 8-)

Wait @bcorrie are you ok with this, too, then?

Seems fine to me as long as cell_id stores the gid/pid and doesn't get redefined to be the "original" identifier (whatever "original" means).

If so, does that mean:

We've solved #347?
You are not interested in an Audit object (etc) otherwise?

Wait @bcorrie are you ok with this, too, then?

Seems fine to me as long as cell_id stores the gid/pid and doesn't get redefined to be the "original" identifier (whatever "original" means).

I think so - we have a different field to store the adc_tool_cell_id ("the original id") or whatever we call it as an ADC extension, so cell_id is your AIRR cell_id, a field whose uniqueness is AIRR context (file, analysis, ADC) specific.

If so, does that mean:

We've solved We need a more formal, fully-qualified identifiers for repository objects #347?

Not so sure, as this is just one identifier that we need to consider, but similar principles might apply

You are not interested in an Audit object (etc) otherwise?

I am interested, I just don't think it is required to resolve the cell_id issue...

I am interested, I just don't think it is required to resolve the cell_id issue...

What is the plan to solve this issue with other _id fields? Eg, clone_id.

Your kidding - right? (eye roll)

No I'm not (heavy sigh), so here's my rant. You do generate a lot of churn with your comments waffling between the very specific and the overly general long-winded platitudes so everybody has to spend a lot of time going back and forth to figure out WTF you actually want. When I initially pointed out this provenance issue initially, your whole response revolved around complaining about the field names, which finally after all of this roundabout didn't freaking matter to you. You could have saved us all a whole bunch of time by just responding to an apparent decision, by simply responding, "no, please, don't go with the custom field route, this is about data provenance and we should have a formal set of fields". Now eventually you got there, but not before a ton of comments about id fields cannot be changed, id fields cannot be changed, id fields cannot be changed, ad nauseum. During this whole, you were fixated (yes) on your solution which was we have to create new gid/pid fields, we have to create new gid/pid fields, we have to create new gid/pid fields, also ad nauseam. When I tried to explain that we should use the existing AIRR _id fields instead of creating new ones, your response was some platitudes that didn't get us closer to the solution. It made me serious wonder if you even understand what we were proposing. I couldn't understand why you refused to consider our solution. Instead of acknowledging that cell_id could be the gid/pid, you were constantly putting up road blocks with apparently reasons why that cannot be or going off on tangents. It didn't seem to click until I was able to get you to respond to a simple question about field names. Or maybe you understood the whole time and was just trolling everybody?
So no I was not kidding when I felt you were fixated. If it rubbed you the wrong way, I say good, maybe you need some self-realization to understand that your comments don't always help. More discussion is not always better. If you need to rant about how great you are to make yourself feel better, fine. I won't burst your bubble by responding to your questions. But you should do a few things. You should spend more time trying to understand the issue and the solutions posed. Ask short pointed questions, instead of writing long rambling comments. You should spend time to understand others viewpoint and why they are posing the solution they are. You should spend less time offering contrarian views that generate constant conflict because it take longer to generate a solution and requires extra effort from everybody. You should instead focus on constructive criticism by actually suggesting changes that push us closer to a solution. Your general MO is to make broad statements, then let everybody do the hard work of posing concrete solutions which you then pick apart instead of (rarely) offering concrete changes. You aren't our manager, and you aren't solely responsible for deciding what work is important and when. It's disrespectful to the rest of the community members when you push that dynamic on them. You have the largest development team of anybody here yet your developers have rarely (if ever) contributed code or contributed documentation, yet you expect us to do all the work for you.

We've solved We need a more formal, fully-qualified identifiers for repository objects #347?

Almost @scharch , we need to decide on some specifics. I suggested these two solutions. I think 1 is the way to go, but wanted to offer 2 in case somebody had compelling reasons why that was better. In particular, IEDB does 2 and the current GermlineSet suggests also, but neither feels "better" to me. We should pick one solution for all AIRR objects to follow.
Then we actually have to decide on the structure of the identifier itself. While we can say CURIE-like, we should be specific about what we actually mean, because we have to specify how the resolvers work.

No I'm not (heavy sigh), so here's my rant.

TLDR 8-)

You should spend more time trying to understand the issue and the solutions posed.

Short answer - I don't agree
Until you try and integrate all the components, like we have, I would suggest that maybe others need to spend more time trying to understand the issues that we raise...

DARN!! Looks like I missed the season finale! Did we already discover that @bcorrie  and @schristley are actually the same person? And get to the point where that person -- after being implicated in the demolition of a good chunk of SRA's infrastructure -- needs to go into hiding and starts setting up Rogue AIRR Repos on Raspberry Pis along Interstate 84? I wonder what kind of global IDs you would need for that! What a cliffhanger!

DARN!! Looks like I missed the season finale!

A doozy for sure. Like every good season finale, it left us with a cliff hanger with Scott pondering life as a blockchain developer instead, which caused Brian to fret that he would no longer be able to spend his days writing poetic treatises on his brilliance but instead might have to learn this python thingy with the colons, tabs and what-not.
And as always they show us snippets of the next season, including:

Scott losing his life savings in a rug pull when he mistakenly buys doggecoin instead of dogecoin.
We also see Scott discovering a bug that the http DELETE method had not been disabled and then manages to delete all of the AIRR Data Commons. For completeness, he deletes all of the AIRR community repositories. When asked what happened, his only response is "oops!"

While with Brian:

After almost 100 commits to fix one line in the yaml file, he declares, "I hate colons... and spaces too!"
He recovers by browsing the issue about extending clone for single cell, which inspires him into the iReceptor trenches where he attempts to stick single cell data into a clone object, only to discover it doesn't work, and in his excitement he creates a new issue exclaiming "clone doesn't work with single cell!", then pats himself on the back for making such a vital contribution to the community.

Meanwhile:

sciReptor comes alive and rampages across Europe eating all of the laboratory mice. This leads Corey to exclaim, "well I guess we don't have sequence the loci of those mouse strains!" IMGT responds, "there are mouse strains?"

Coming to you all on the AIRR+ streaming network, for only $29.95 a month!

Heh. Sounds like we have some communication issues to sort out. Which are super important, because we can't do anything if we can't communicate, but I think we can handle that via other channels. They don't need to be part of the WG's permanent record. Feel free to drag me into an email thread if you want my opinion. I suggest we delete the rants and get back on topic, if we have anything left to discuss regarding identifier provenance.
The good news is it looks like we've arrived at a solution! Which is to add some sort of ID history fields to the ADC Rearrangement extension for at least sequence_id and cell_id.
Because this is essentially a custom field solution, I don't have an opinion on implementation. Just some loose suggestions on future-proofing:

Do the same for clone_id.
Use a suffix other than _id to avoid confusion. Eg, _ref, _rid, _fd, _comment, etc. Dependent upon how we resolve persistence (#347) and whether you want this to be primarily an identifier in a file.

I assume we can table the Provenance and Audit ideas, yes?

Heh. Sounds like we have some communication issues to sort out.

Certainly, it's one thing if it's constructive discussion, but statements that imply that mine and others input isn't relevant, and furthermore, that we don't consider all the issues brought forward and don't spend a lot of time trying to understand, is just insulting. This condescending and demeaning behavior has been going on for years.
 I didn't sign on for, nor do I wish to participate in, such a toxic environment. I've decided to completely disengage from the AIRR Community until further notice.

@schristley, understood. I'll follow up separately about whatever work needs to be done.
I'm going to go ahead and clean up this issue.

closed for AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUGGGGGGGGGGGGGGGGGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH


Bug: fixed column with rowspan table, the plugin bring the width of narrowest 1st column to use

Topmost first row and column is colspan=2, I prefer that will bring the width of the first cell in the first place.

@xenogew Please see this demo: https://wingmeng.github.io/fixedThead/test/demo6.html

Now I can solved it, thanks.


Max 1800 tokens per batch?

I found in the latest version, there seems to be a maximum token limitation up to 1800 in a batch. Can I change this setting? I found the gpu memory is not fully used.

yes you can change this with -max_tokens
it all depends on the size of your network and your gpu memory.


Enable/Disable Resources

https://github.com/firezone/firezone/issues/2667#issuecomment-2209392840

I'm still thinking of what's the best design for this.
Either the client could inform the disabled/enabled routes to connlib, or it could just save the state of disabled/enabled route and filter routes based on that.
However, I think it's better to let connlib decide the routes and have the client just pass the UI information to connlib.
The main reason for this, is that connlib only pass the routes to the clients and not what resources enabled those routes, so for overlapping internet resources it could be complicated for the client to ignore routes w/o making assumptions on how those routes are selected from the resources, which I think is better that we keep in connlib.

Test #4834 to see if full-route fixes it

I'm still thinking of what's the best design for this.
Either the client could inform the disabled/enabled routes to connlib, or it could just save the state of disabled/enabled route and filter routes based on that.
However, I think it's better to let connlib decide the routes and have the client just pass the UI information to connlib.
The main reason for this, is that connlib only pass the routes to the clients and not what resources enabled those routes, so for overlapping internet resources it could be complicated for the client to ignore routes w/o making assumptions on how those routes are selected from the resources, which I think is better that we keep in connlib.

Also, doing it on the client would require us to implement this functionality multiple times.
I am in favor of introducing messages for enabling / disabling resources. Likely, we want the state to be ephemeral in connlib, so the client has to disable resources every time it boots up a new session.

Hi, this issue is closed but I'm unable to find how to enable/disable resources in latest clients. Is there an extra thing I need to do?
I think this feature is very important. In our company, tech people often have access to prod and staging and it could be great for them to be able to disable prod resources if they are not using them in order to avoid mistakes.
I saw the PAM issue and I think it's a good first step but beeing able to disable a resource from the client is pretty important I think. Ofc, not all resources should be disableable and it should be configured through a policy or directly in the resource.

@Intuinewin So enable/disable is only supported for the Internet Resource -- we wanted to think more carefully about the use cases there before adding complexity that might already be handled by #6158. One of the use cases for that issue is specifically preventing prod access.


Feature request: import module from common directory

For my current latex workflow, I have a common.tex at ~/texmk/tex/latex/commonstuff/ which can be included via usepackage directly using latexmk without specifying the relative or absolute directory, and it is used in all my paper and notes. I really wish I can do the same in typst. As of what I know, typst doesn't have such commonstuff directory? And, as a generalization of this idea, is plugins or even package managers planned for future? The modular design typst currently has is really suitable for such plugin system.
No matter what, thanks for creating such an amazing project!

A package manager is planned. For now, a common directory could be realized by setting TYPST_ROOT to that directory and then using absolute paths with leading slash to import from there and relative paths otherwise. Note that TYPST_ROOT was only recently merged and is not in the latest release. In the future, we might also have a better solution for such a common directory.

I'm really interested in contributing to the project. Is there any way to get started, e.g. good first issues?

A package manager does not solve the use-case where I want to define a template locally, and have it accessable in any (local) typst document I create regardless of file location. Is that use-case covered elsewhere, or was this issue closed a little prematurely?

You can make a local package: https://github.com/typst/packages#local-packages

True. That is a decent fix for now.
Ideally there would be a config file (toml/yaml or something similar) where one could add a path, and when including a file, if it is not found in the local directory, it is looked for in that path. That would be better because it would

allow arbitrary file locations,
avoid having to make a rigid folder structure just to define a template, and
turn #import "@local/mypkg:1.0.0": * into #import "template1.typ": *. I would likely have to look up the former style several times, and find it a hassle having to think about versioning of a simple local template.

It also seems like something that would be simple to avoid breaking, whereas the local package solution has a warning about potential future breakage.


[security/tinc] Enable usage of no, one or several addresses per hosts

All three situations are legit, both for local and remote hosts.

@ElNounch did a small test on my end, looks good, I only added a new version number in https://github.com/opnsense/plugins/commit/5dc2478cd7e31069b6a5fadb8750a1fc6cfb20b8 and merged the PR.


EfficientDet: Are you going to implement this in the object detection API?

System information

TensorFlow version (you are using): 2.0

Describe the feature and the current behavior/state.
I read about this new Network topology: https://arxiv.org/pdf/1911.09070.pdf
It seems to work precisely and fast. Are you going to implement this new topology to your framework?
Will this change the current api? How?
Possible
Who will benefit with this feature?
Everyone who works with object detectors!
Any Other info.
If the answer is yes: will there be a quantized version for TPU inference?
Thanks in advance,
Timo

Linking a community-built implementation of EfficientDet in TF 2.x in the interim. Thanks, @Guillem96!

@dynamicwebpaige I am still working with it. My intention is to override train_step method of my EfficientDet class, just as tf 2.2.0 style , and get the .fit method extra features (TPUDistribute strategy, logging, callbacks,...) for free.
Thanks for linking my implementation here 😃

@TimoK93
It's now available in the TensorFlow 2 Detection Model Zoo
https://github.com/tensorflow/models/blob/master/research/object_detection/g3doc/tf2_detection_zoo.md

@TimoK93,
Sorry for the delayed response. EfficientDet is present in the Model Zoo as well as in Tensorflow.org.
Thanks!


Actually, just remove  the link but leave the note. sorry

Issue in /src/pages/implement/client-side/atjs/target-atjs-versions.md

Clarification,:
The request is to remove the link under the "at.js Version 1.7.0" section, as it points to this same page.


Location Always second modal not popping out in IOS

Bug report

Summary
My use case is to route the user to home screen after he enables location always. Reading the docs there is a second modal that should come out after enabling the first one with "usage only when app is opened" but it doesn't come out and it only returns as if the user did enable the location always. After a while (30 minutes or so) the modal sometimes comes out but that is not the expected behaviour.
Environment info

react-native info output:
System:
    OS: macOS 11.2.3
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 112.46 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.1.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.11.2 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 21, 22, 23, 24, 25, 26, 27, 28, 29, 30
      Build Tools: 21.1.2, 29.0.0, 29.0.1, 29.0.2, 29.0.3, 30.0.3
      System Images: android-21 | ARM EABI v7a, android-21 | Intel x86 Atom, android-21 | Intel x86 Atom_64, android-21 | Google APIs ARM EABI v7a, android-21 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom_64, android-29 | Automotive with Play Store Intel x86 Atom, android-29 | Android TV Intel x86 Atom, android-29 | Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64, android-30 | Google APIs ARM 64 v8a, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play ARM 64 v8a, android-30 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64, android-S | Google APIs ARM 64 v8a, android-S | Google APIs Intel x86 Atom_64, android-S | Google Play ARM 64 v8a, android-S | Google Play Intel x86 Atom_64
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>99119
    Xcode: 12.3/12C33 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_282 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.3 => 0.63.3
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 3.0.3
Steps to reproduce

run requestIOSLocationPermissions function
press on enable locations when in app
second modal will not popup and you will get a response as if you have the permission

Describe what you expected to happen:

Promp first modal to allow location only when app is in use
Promp second modal to allow location always
Receive location permission
route to home screen

Reproducible sample code
export const checkIOSLocationPermissions = () : Promise => {
return check(PERMISSIONS.IOS.LOCATION_ALWAYS)
.then(async (statuses) => {
if (statuses === RESULTS.GRANTED) {
if(SYSTEM_VERSION >= 14){
const isAccuracyFull = await checkIOSAccuracy();
return isAccuracyFull ? true : false;
}
return true;
}
return false;
})
}
export const requestIOSLocationPermissions = () : Promise => {
return request(PERMISSIONS.IOS.LOCATION_ALWAYS).then((statuses) => {
if (statuses === RESULTS.GRANTED) {
return true
}
return false
})
.catch((error) => {
console.log('ERROR-requestIOSLocationPermissions', error )
return false
})
}

The modal will appear later with a message "App has been using your location in the background", when your app is closed.
That's the expected behaviour, see the Apple documentation: https://developer.apple.com/documentation/corelocation/cllocationmanager/1620551-requestalwaysauthorization#3578736


Trimmer executing mutliple times?

First of all, sorry for asking you that much maintenance for an as little plugin.
I hope that I'm making a mistake but maybe the trimmer is executing multiple times?
Tell me if I'm wrong
local vim = vim
local api = vim.api
local cfg = require'trim.config'

local c = 0

local trimmer = {
  trim = function ()
    local save = vim.fn.winsaveview()
    for _, v in pairs(cfg.patterns) do
        c = c + 1
      api.nvim_exec(string.format("silent! %s", v), false)
    end
    vim.fn.winrestview(save)
        print(c)
  end
}

return trimmer

Ouput :
4
8
12
16
20

Have a nice day!

hmmm...
In my environment, it did not reproduce the problem, only 4 is output.
(Of course, each time I write, the number increases by 4.)
Could you tell me your config for this plugin, please?

I've reproduced it!
I only had one disable in my config, so it happened to work.

This problem should have been fixed by https://github.com/cappyzawa/trim.nvim/commit/bd1565207bd0ac211240641322cfaf70253bc3d5.
Could you update this plugin and test this again? 🙏

It seems to work!!
For this config :
    use {
        'cappyzawa/trim.nvim',
        event = 'BufWritePre',
        config = function()
            require('trim').setup({
                disable = {"json", "javascript", "css"},
                patterns = {
                    [[%s/\s\+$//e]],
                    [[%s/\($\n\s*\)\+\%$//]],
                    [[%s/\%^\n\+//]],
                    [[%s/\(\n\n\)\n\+/\1/]],
                }
            })
        end
    }

I have an output of 4
So it's prefect, have a good day!


Export the cost analysis to a storage account with selected network

Due to my company restriction, I have to export the cost analysis report to a storage account with selected network. In the storage account, I've enabled the MS trusted services. But it seems the Excel can't export to the destination and being blocked. Are there any workaround?

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

ID: 51144539-a3a7-f7fa-1bc1-0d32bb85e9fd
Version Independent ID: b01d33a0-4c5d-7ec4-8c2f-de4a940707dc
Content: Tutorial - Create and manage exported data from Azure Cost Management
Content Source: articles/cost-management-billing/costs/tutorial-export-acm-data.md
Service: cost-management-billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@HansonChiu1994 Thanks for your comment! We will review and provide an update as appropriate.

@bandersmsft Any thoughts on this?

@HansonChiu1994 Investigating this with the engineering team.

@HansonChiu1994 Sorry you've ran in to this situation, which is a bug. Currently exports doesn't   support storage accounts with an active firewall, but we're working on it.
For now, the work around is to use a storage account without a firewall or use the Usage Details API to download the usage file locally.
#please-close

Hello @bandersmsft it has been almost two years when first issue with cost exports has been raised. And today I found out that there is still no fix. Do you have some any new information it this is going to be solved or not? Thank you.

Hello @bandersmsft it has been almost two years when first issue with cost exports has been raised. And today I found out that there is still no fix. Do you have some any new information it this is going to be solved or not? Thank you.

@maniaX1 Hi there. I'll check with the engineering team, but I think this issue has not been solved. I'll reply here when I have confirmation.

@maniaX1 Hi there. I'll check with the engineering team, but I think this issue has not been solved. I'll reply here when I have confirmation.

Can this issue be reopened or should we open a new issue for this to track this?
A firewall-less deployment, as suggested, is not a usable workaround for this issue.
Best

hello @gxtaillon  - sorry for the delay. My recommendation is to open a new issue.
@bandersmsft  - FYI

Does any one have the link to the new issue referenced above?
When we reached out to MS Support on this issue, we were told that it is as per the current design and there is no immediate plans to address this for storage accounts behind firewall.
Not sure why MS has not addressed this obvious requirement

Any update on this plesae?

Support for cost export to storage account behind firewall has been enabled since Sept 2023. I am able to successfully configure it as well for our data lake.
https://azure.microsoft.com/en-us/updates/exportbehindfirewallga/
https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/tutorial-export-acm-data?tabs=azure-portal#configure-exports-for-storage-accounts-with-a-firewall


Added Staging Details.

Added some detail about the specific stages of TronScriptEvo

Thanks for this, incredibly helpful!

No probs, I figured it'd be helpful either way.


security concerns with timing attack in bn.js use

I think https://github.com/crypto-browserify/diffie-hellman/issues/22 is also applicable here.

We use a blind in our calculations just like how libressl does, if you had
read through the DiffieHellman issue you would have noted that the issue
there is a different type of constant time thing they use in libressl that
I'm not sure how to replicate in JavaScript, any ideas there would be
helpful.
If I'm misreading your comment you think there is a flaw in how we are
doing the blinding in this library or there is an additional safeguard we
can use I'm all ears.
That being said this is a port of the nodejs api which is frustratingly
synchronous so we are unable to take advantage native crypto abilities in
the browser so I'd honestly be very hesitant to recommend this for anything
other then verification
On Tue, May 2, 2017, 11:05 AM Pirate Praveen Arimbrathodiyil <
<EMAIL_ADDRESS>wrote:

I think crypto-browserify/diffie-hellman#22
https://github.com/crypto-browserify/diffie-hellman/issues/22 is also
applicable here.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/crypto-browserify/browserify-rsa/issues/11, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABE4nwK5sOKfQF9FG-N3m6Yb6CLuZBe6ks5r1vHzgaJpZM4NN4uo
.

I was just confirming since this library also uses bn.js. Thanks for your comment.


Pull utilities methods out into an lvlib

A number of the (previously) private methods in VeriStandTestCase do not actually have requirements on the test case; they previously had been located there for convenience. As we explore writing tests for the testing tools, it is becoming apparent that some of these methods are useful on their own, and could be used without VeriStandTestCase to build up more complex functionality.
This change pulls out the majority of the methods in VeriStandTestCase into an lvlib. The few VIs remaining in the Utilities/ directory are primarily implementation details or glue code that (IMO) do not make sense to expose. The intent is to unit-test the now public functionality of VeriStandTestUtilities.lvlib, and write integration tests for the functionality in VeriStandTestCase.

It looks like when I applied the lvlib utilities icon header it applied numbers to a bunch of the VIs. I'll remove those, but this p.r. is otherwise good to review.
We should add useNumbersForNewVIIcons=False to the list of config options to set.


Remapping m

Hello,
for some reason I am not able to make the following remap work: nnoremap <Leader>m m..  Actually, I cannot make any remap involving m + <command>, for example nnoremal <C-L> ma. My leader is the space key, and I did not remap : (I remapped , to : though)

I'm not sure I understand the issue.

Do you have the default mappings for Signature and is that when you're facing this issue?
Where are you trying to do nnoremap <Leader>m m.

Yes, I have the default mappings. I am trying to put that into my .vimrc
but it doesn't even work from inside vim
On Sat, Jun 20, 2015, 01:51 Kartik Shenoy<EMAIL_ADDRESS>wrote:

I'm not sure I understand the issue.

Do you have the default mappings for Signature and is that when
you're facing this issue?
Where are you trying to do nnoremap m m.

—
Reply to this email directly or view it on GitHub
https://github.com/kshenoy/vim-signature/issues/87#issuecomment-113674527
.

Hey, sorry, I've been really busy at work lately and it's only going to get worse with projects coming to a close :(
I'll try to work on this but can't promise it'll be any time soon.

No worries, be strong and good luck! Thanks for your work ;)
On Tue, Jun 23, 2015, 21:41 Kartik Shenoy<EMAIL_ADDRESS>wrote:

Hey, sorry, I've been really busy at work lately and it's only going to
get worse with projects coming to a close :(
I'll try to work on this but can't promise it'll be any time soon.
—
Reply to this email directly or view it on GitHub
https://github.com/kshenoy/vim-signature/issues/87#issuecomment-114620438
.

Doh! I missed the obvious bit here. 'm' is already mapped to :<C-U>call signature#Input()<CR>
That's why if you use nnoremap <C-L> ma, you trigger only the default behavior of 'm' and not the new one.
Check this Stack Overflow reply for details.
You can make the maps by simply using nmap instead of nnoremap
nmap <Leader>m m.
nmap <C-L> ma

Hope this helps

It works, thank you!


Title tags issue

I recently created ts template using this starter. When I deploy it to vercel, it shows the url in the browser tab instead of the actual .... Locally it works fine. On Google it indexes fine. But when you open site, this is how it looks like:

When I inspect the website,   tag is empty.

But if I see the page source, it is fine. I am not sure what is going on here. I tried other browsers as well. It is same.

Can I check that siteMetadata.title has been filled and that the title is being passed to the pageSEO component? If so, could you link the repo and website and I could help take a look.

For sure, here is the repo. Here is the site metadata and it is being passed to pageSEO component in index.

You must have cloned the repository from the Vercel "deploy" button? It seems like it automatically bumps next.js to the latest canary version which is 12.1.7-canary.30. It looks like they are making some big changes in preparation for nextjs 13 which might potentially break how the head component is rendered. I will take a look at the issue when it is officially released - strange that it works locally but not on Vercel. In the mean time, downgrading next.js to 12.1.6 fixes the issue!
I also see that you are on the typescript, non-contentlayer branch which I no longer intend to maintain. It will still work perfectly fine, but could I suggest trying out the new project?
To bootstrap a new blog, run
npm i -g @pliny/cli
pliny new --template=starter-blog blog-name

I think the developer experience is much nicer with the new template :)

Thank you so much for taking a look and getting back quickly.
Bumping down the version solved the issue. It is surprising to me, even the generated static files had the title and everything still they did not show up. I will definitely give the new project a try.


RTL version

Possible to make this dashboard RTL?

Hello, yes of course, there is an option. you can checkout in the demo


N20: Release

Preview (https://github.com/rust-gamedev/rust-gamedev.github.io/commit/4d55e74ad1e5a49680bc18037823f0a6493435b9): https://rust-gamedev-preview.netlify.app/posts/newsletter-020
Everyone is invited to review!
:timer_clock: Merging this in ~4/5 hours if there're no objections.
Part of #531

e.g. posting issues on our github.

This contradicts the guidelines, I think. Shouldn't be written as "our".

Station Iapetus

Has both the image as a link, and the link in the image caption. Should the caption just say "click on the image to see the video", or the image be non-link instead?

Emerald

The image here doesn't need to be so big, since it's just a logo, it doesn't show any actual rendering.
Honestly, this entry is also a bit fishy... The news for Emerald are just these two tiny lines:

rendering to textures
WASM game sample.

While everything else is self-promotion and general information. I think the newsletter should put a stronger focus on the "news" part, and prevent parties from just using it to remind about themselves. I.e. something like "your news need to be at least as big as the general description" rule.
Similar concern could be applied to "Quinn" entry, although to a much lesser degree.
The "bevy" entry style is what I find to be the best, and every entry should try to follow the format.
In "wgpu" entry, something goes wrong about the image caption, it's not centered.

(such as #[allow(unused_attributes)])

Would be nice to codify this part (i.e. with "`")

based on the wgpu framework

nit: wgpu is a library, not a framework

@kvark addressed most of the suggestions, thanks!

The news for Emerald are just these two tiny lines:
While everything else is self-promotion and general information. I think the newsletter should put a stronger focus on the "news" part, and prevent parties from just using it to remind about themselves. I.e. something like "your news need to be at least as big as the general description" rule.

This is the first newsletter issue that features Emerald's entry. It's ok that it focuses on a general overview.

Similar concern could be applied to "Quinn" entry, although to a much lesser degree.

Same with Quinn.

:timer_clock:  Merging in 15 minutes.

Ok cool, I didn't realise this is the introduction for these libraries :)

On Apr 10, 2021, at 11:31, Andrey Lesnikóv @.***> wrote:

Merged #583 into source.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


"Using Indexers - C# Programming Guide" should mention ref returns

Following statement isn't quite correct.

An indexer value is not classified as a variable; therefore, you cannot pass an indexer value as a ref or out parameter.

But you can pass an indexer value as a ref, if the indexer uses ref return, like this.
        private readonly int[] arr = new int[10];
        public ref int this[int index]
        {
            get
            {
                return ref arr[index];
            }
        }

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

ID: 5323b38b-8dc5-8f50-f5e7-b58ca0e88ad7
Version Independent ID: 3d9a83cd-98e3-fc6e-727b-32c8e9228c69
Content: Using Indexers - C# Programming Guide
Content Source: docs/csharp/programming-guide/indexers/using-indexers.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for spotting this. We'll get this updated.


Create the participant_project_species table, used to link species with projects and provide submission status and feedback

Create the participant_project_species table, used to link species with projects and provide submission status and feedback
Add comments to table and add to schema docs generator

#1919
#1918
#1917
#1916  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite


Traffic law in the United States

If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
Describe the contribution to the taxonomy

...
...
...

Input given at the prompt

   ...

Response from the original model

  ...

Response from the fine-tuned model

  ...

Contribution checklist

[ ] The contribution was tested with ilab generate
[ ] No errors or warnings were produced by ilab generate
[ ] All commits are signed off (DCO)
[ ] The qna.yaml file contains at least 5 seed_examples
[ ] The qna.yaml file was linted and prettified (yaml-validator can do both)
[ ] An attribution.txt file in the same folder as the qna.yaml file
[ ] Content does not include PII or otherwise sensitive or confidential information
[ ] Content does not include anything documented in the project's Avoid these Topics guidelines

@jjasghar I'm not sure why I cannot push my changes. Is this something you can help with?
 $ git push origin mburke5678-patch-1
Gtk-Message: 09:05:31.257: Failed to load module "canberra-gtk-module"
Gtk-Message: 09:05:35.234: Failed to load module "canberra-gtk-module"
remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/mburke5678/taxonomy.git/'

 $ git push origin mburke5678-patch-1

Is origin: mburke5678:mburke5678-patch-1?

Can you show me the most recent command you used to push?
When it comes to GitHub I'm limited in the amount of help I can give you due to the different ways one can set it up. Please understand that.

Is origin: mburke5678:mburke5678-patch-1?
@jjasghar Yes.

if you run ssh<EMAIL_ADDRESS>on your command line what comes back?

There might be an issue with the SSH key here in the repo, I think this might help https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account

Closing per combined PR here: https://github.com/instructlab/taxonomy/pull/1151


Add MockTcpServer, DaytimeTCPClient integration tests

Adds MockTcpServer - base class for all other TCP Server impls, e.g. we can have MockDiscardTCPServer to test DiscardTCPClient or MockEchoTCPServer to test EchoTCPClient
Adds MockDaytimeTCPServer that uses the given clock to mock returned daytime string
Adds DaytimeTCPClient integration tests

FYI
@garydgregory @kinow @sebbASF

@jkbkupczyk
Thank you for PR.
Please add a brief class level Javadoc to each new class.
Files should end in an empty line.

@jkbkupczyk Thank you for PR. Please add a brief class level Javadoc to each new class. Files should end in an empty line.

Thank you @garydgregory for review :)
I added missing Jacadocs and rebased onto master.

Hi @garydgregory, any new comments regarding this PR?

-1 as the PR stands today: The PR does not test anything new that isn't already tested.
Before and after this PR, the code coverage is the same at: 40% instructions / 31% branches.
Run mvn clean site -Pjacoco then open target/site/jacoco/index.html
Or am I missing something?

-1 as the PR stands today: The PR does not test anything new that isn't already tested. Before and after this PR, the code coverage is the same at: 40% instructions / 31% branches. Run mvn clean site -Pjacoco then open target/site/jacoco/index.html Or am I missing something?

Hi, @garydgregory
I ran mvn clean site -Pjacoco both on master and mock_tcp_test_server_daytimetcpclient_tests and these are the results I've got:
master

mock_tcp_test_server_daytimetcpclient_tests

did you check site/jacoco/org.apache.commons.net.daytime/DaytimeTCPClient.html?

@jkbkupczyk
Well, it works for me now locally. Merged! Sorry about the delay.


Update approval-admin.md

Adding changes for the Templates feature that will be added to the Approvals App

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Tile y-sort origin is not center

Godot version
4.0.dev (79d6c2ceb9)
System information
Arch Linux
Issue description
The tile origin used for y-sort is not the center of tiles in Godot 4. It is currently the top of tiles just like it was in Godot 3, but according to @groud it was intended and expected to be the center in master.
I was having a conversation in Discord about this and ultimately ended up recording a video to capture the problem in the form of a video:  https://www.youtube.com/watch?v=MgmuR-ZC8PA
This video's intent was more about asking how we can change the value, but supposedly what I actually uncovered was that the intended default of using the center of tiles was not being respected.
If the default for tile-origin was indeed the center, this would make a much better user experience and I would imagine most people would rarely or never even need to override the tile-origin. As it stands though, with a default of the top of tiles, it would need to be overridden for just about every non-ground/path tile (trees, buildings, signs, chests, etc.).
For this reason I never understood why the default was TOP_LEFT in Godot 3 (bearing in mind the "_LEFT" part is irrelevant anyway for y-sort), and was very happy to hear that the default was changed in Godot 4, even if it's not currently working as intended.
Steps to reproduce
The video linked above shows my minimal example in video form, but it can be distilled even further:

make TileMap
enable y-sort on it and its parent
observe that it is essentially impossible to get the y-sort to kick in (change render order)

This is because the y-sort tile-origin is not the center by default, it is the top of the tiles.
Minimal reproduction project
godot-3-tile-origin.zip
godot-4-tile-origin.zip

Ok I tested and likely figured out the problem (I tested on my branch which is a little bi t different). Two things:

The polygon origin should likely be at the bottom of the polygon, to make it work like a character I suppose. On my side I thus moved the polygon to have it on top of the KinematicBody2D node's position.
You need to activate Y-sorting on the TileSet resource, in the rendering section. This is needed right now on master but since I am implementing Tilemap layers, I'll most likely remove it from the TileSet resource.

Let me know if it helps.

Oh okay, this did work. Thanks!
I'm going to close the issue, but feel free to open it back up again if you want.


Expose static backup data

This PR exposed the static backup file from the node.
The goal is to persist the up to date static backup file locally for a case where the node is not available to serve that file.
Still missing the React Native (Hope to use the generator for that).
fixed https://github.com/breez/breez-sdk/issues/437

You can run the RN codegen on this now :wink:


(Build) Fail on dev branch.

This issue is created automatically by CI.
Linux Build State: failure
Windows Build State: success
Commit: 68ca63a3e7486baf38dffa37d60292d05fb1580a
Commit Branch: dev
Commit Author: innerviewer

Auto-closing as build in this branch is successful now. Commit: c1fa043bef67f16c3ed57ce2e68f73ba379e273b


Improved PersistentId support to not depend on hash of email, or urls of service provider or identity provider

The current system generates persistent ids from the default nameid (usually email), and SP and IdP entity ids (generally URLs). A user email, service provider url, or identity provider url might change over time. In the previous system, this would change the PersistendId, leading to possible account loss on the client side. By using a random uuid stored in the database, this risk is alleviated.

Fixed in favor of new PR to master


focus triggered on incorrect field after scroll.

Hi everyone,
We're using fastclick in an iOS web application, and are encountering an issue with focus and fastclick.
See the fiddle here:
http://jsfiddle.net/xJrsW/
open this URL in iOS: http://jsfiddle.net/xJrsW/embedded/result/
The problem occurs when the iPhone scrolls as a part of focusing the field.

I scroll the to the very top of the document:
I tap (and hold) on textfield 3, then release
textfield 5 focuses

the problem is intermittent, and a simple quick tap on #3 does not cause the problem.
Any ideas on what might be going on?
Thanks!

I was able to fix this in my app by returning false in FastClick.prototype.onTouchEnd for text and textarea inputs :
@@ -522,6 +522,13 @@
 	FastClick.prototype.onTouchEnd = function(event) {
 		var forElement, trackingClickStart, targetTagName, scrollParent, touch, targetElement = this.targetElement;

+		// Takes care of https://github.com/ftlabs/fastclick/issues/36
+		if(deviceIsIOS &&
+				targetElement.nodeName.toLowerCase().match(/input|textarea/) &&
+				targetElement.type.toLowerCase().match(/text|textarea/)){
+			return false;
+		}
+
 		if (!this.trackingClick) {
 			return true;
 		}

This probably doesn't scale to all use cases but I think it's a start.

This causes an issue in iOS when time is changed to a previous date. I was thinking about taking the absolute value in
if (Math.abs(event.timeStamp - this.lastClickTime) < 200) {     event.preventDefault(); }
Could that cause other problems?

hi, everyone:
when I use 'vue'.
some dom like it :
<p @click="active=!active" :class="active?'active':''">toggle</p>
and use 'fastclick' like it:
FastClick.attach(document.body)
I quickly click 'P' two times.
the chrome F12 is warn:
Unable to preventDefault inside passive event listener due to target being treated as passive.See https://www.chromestatus.com/features/5093566007214080;
so, I use the @jdurand method.
such as :

// Prevent phantom clicks on fast double-tap (issue #36)
     if ((event.timeStamp - this.lastClickTime) < this.tapDelay) {
        var target = event.target || event.srcElement;
        if(target.nodeName.match(/input|textarea/i)){
            event.preventDefault();
        }
    };

Could your change the @@ 444,4~451,4 @@ code? thanks!

Same as above


Keras version should be higher when using 2.0.2

Hello,
In the imageai 2.0.1, the keras 2.0.9 is ok.
But when I updated to imageai 2.0.2, there was a RuntimeError:
The Session graph is empty.  Add operations to the graph before calling run()

I think it was because the keras version is not latest, so I updated my keras to version 2.2.4. This problem was solved. I do suggest to add this to the document as the document only listed that keras should be 2.X.
thanks for your nice project

Thanks for sharing this. I will review this and update accordingly.


issue with installing angularcli

npm ERR! code E403
npm ERR! 403 403 Forbidden - GET http://infynexus/repository/npm-all/npm
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy.
npm ERR!      C:\Users\sai.sagi\AppData\Roaming\npm-cache_logs\2020-08-09T14_57_45_584Z-debug.log

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


CRAS not working properly

name: bionic
encrypted: no
Entering /media/removable/Crouton/chroots/bionic...
crouton: version 1-20190403182822~master:174af0eb
release: bionic
architecture: amd64
xmethod: xiwi  (I currently use xorg for heavier stuff)
targets: xiwi,xorg,touch,keyboard,lxde
host: version 11647.104.0 (Official Build) stable-channel setzer
kernel: Linux localhost 3.18.0-19030-g15d00031737b #1 SMP PREEMPT Thu Mar 21 00:23:58  PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

Please describe your issue:
On ubuntu bionic, running alsamixer yields
Couldn't create CRAS client
cannot open mixer: No space left on device

And using  pulseaudio --start yields
N: [pulseaudio] main.c: User-configured server at {c9ef85f42c9b41b8a1d51cb182076c00}unix:/tmp/pulse-PKdhtXMmr18n/native, which appears to be local. Probing deeper.

Also, running cras_test_client --dump_server_info yeilds
cras_test_client: cras_client: Could not setup watch for '/var/run/cras/.cras_socket'. Couldn't create client.

I have already tried an reinstall. If needed (takes about a day on my internet), I can roll back (reinstall) to xenial or artful.
If known, describe the steps to reproduce the issue:
Install ubuntu bionic beaver ('bionic')
try to run the commands above

This seems to be because of chromeos, not crouton. It is mentioned in another issue.

@pcs3rd,

cannot open mixer: No space left on device

That may also be a problem.
Hope this helps,
-DennisLfromGA


docs: Are the online documents down?

Hello,
Not  a document request here , but I'm trying to check the online docs and they don't load. Have they been moved?
https://calm-sea-053fa6a03-365.westeurope.3.azurestaticapps.net/ (404)
https://www.fluentui-blazor.net/Accordion (doesn't load)
many thanks
Vince

I can view it again- thank you


"Object result" parameter is not used leading to "NOT_ACTIVATED" in replication status column when downloading page report content

https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/84fcdd4bc66b020ac7c1a03134d1d7f474ce10e5/bundle/src/main/java/com/adobe/acs/commons/reports/models/PageReplicationStatusModel.java#L103

@insideaem  see also #2509


RuboCop linter gives false alarm syntax error, possibly haml lint specific

The following HAML code results in a false alarm about invalid Ruby syntax in the RuboCop linter:
- choice = {required: 'mandatory'}
= if choice[:required] == 'mandatory' then '*' end

The error given is
Andrews-Air:sandbox_20170620 agrimm$ haml-lint page.html.haml
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.3-compliant syntax, but you are running 2.3.1.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
page.html.haml:2 [W] RuboCop: unexpected token kEND
(Using Ruby 2.1 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)

1 file inspected, 1 lint detected

I suspect that it isn't a RuboCop error, because running similar code in RuboCop doesn't give an error:
Andrews-Air:sandbox_20170620 agrimm$ rubocop plain_ruby.rb
Inspecting 1 file
C

Offenses:

plain_ruby.rb:1:10: C: Space inside { missing.
choice = {required: 'mandatory'}
         ^
plain_ruby.rb:1:32: C: Space inside } missing.
choice = {required: 'mandatory'}
                               ^
plain_ruby.rb:2:1: C: Favor modifier if usage when having a single-line body. Another good alternative is the usage of control flow &&/||.
if choice[:required] == 'mandatory' then '*' end
^^

1 file inspected, 3 offenses detected

The Ruby code is
choice = {required: 'mandatory'}
if choice[:required] == 'mandatory' then '*' end

Version information:
Andrews-Air:sandbox_20170620 agrimm$ haml-lint --version
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.3-compliant syntax, but you are running 2.3.1.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
haml-lint 0.26.0
Andrews-Air:sandbox_20170620 agrimm$ rubocop --version
0.49.1
Andrews-Air:sandbox_20170620 agrimm$ ruby --version
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin14]

Apologies for not running under the latest master commits.

This is how the example is parsed into Ruby:
choice = {required: 'mandatory'}
if choice[:required] == 'mandatory' then '*' end
end

The syntax error occurs because of the end that is inserted on pseudo-line 3. That end is inserted because the = operator currently treats the if that is passed to it as a requiring a block (see HamlLint::RubyExtractor#visit_script and HamlLint::RubyExtractor#start_block_keyword?.
We'll have to figure out a way to check whether the end already exists or not so we only insert it when it's needed.


javascript page navigation doesn't work with DOMContentLoaded

since page navigation is done through javascript, how can i detect page loads and run js/ts code when a specific page is opened/previewed, DOMContentLoaded doesn't work, const init doesn't work.

see the "nav" event
https://quartz.jzhao.xyz/advanced/creating-components#scripts-and-interactivity

thanks a lot


fix steps order in circleci and revert update on docs

:tada: This PR is included in version 1.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added bitwiser-material theme

Great. Thanks. Cheers. Note: There's a merge conflict - will add your theme "by hand.".

@brijeshb42  Added theme "by hand". It's now live. Thanks again. Cheers.

@geraldb Thanks


" API call threw an Exception"

Hi
I am running the Basic Console Sample( C#), I have built the project with no errors. Although new frames/faces are acquired and submitted. There is the following error  on the console " API call threw and Exception".
I have already entered the Face API Key to the Program.cs file.
Any idea of what I might be doing wrong?

Hi @Almaas,
It sounds like you're trying to use the C# sample for the Face API, correct? A few months ago, we broke out each project in this repo into separate repos. As such, the new repo for Face can be found here: https://github.com/Microsoft/cognitive-face-windows.
We have made updates to the Face-Windows repo over the past few months. I would start by pulling the latest code, inserting your API key, and seeing if you can run it without errors. If you still run into an issue, feel free to reach out on StackOverflow: https://stackoverflow.com/questions/tagged/microsoft-cognitive.
Thanks!


Maybe release? Rails 6 is broken(

Rails 6 is not working with the latest release (AR configuration changes), but works fine with the lates master (thanks to this commit
https://github.com/pat/combustion/commit/3c4bc97e0ff7870c1589bcdbc1c41b3966932eb6).
Any plans to release it?
P.S. Thanks for the great gem)

Just released v1.1.0 which includes the Rails 6 fix :)


Generate data for landing page dropdowns

[ ] Create list for lines dropdowns. Try to make this based on the line changes spreadsheet.
[ ] Create lists for stop dropdowns

Merged into dev


Cannot install latest ruby through chruby on Mac M2 Apple Chip

Description
Cannot install latest ruby through chruby on Mac M2 Apple Chip
Steps To Reproduce
Steps to reproduce the bug:

brew install chruby ruby-install xz
ruby-install ruby

Actual Behavior
>>> Updating ruby versions ...
!!! Failed to download https://raw.githubusercontent.com/postmodern/ruby-versions/master/ruby/versions.txt to /Users/ppwang/.cache/ruby-install/ruby/versions.txt!
!!! Failed to download ruby versions!

Environment
$ chruby --version
chruby: 0.3.9

This does not appear to be a chruby issue, but could be a network or SSL related issue, or maybe related to ruby-install. Have you tried to manually download the file with curl or wge to test whether it is a networking or SSL related issue?
If your system has curl installed:
$ curl -f -L -C - -o /Users/ppwang/.cache/ruby-install/ruby/versions.txt https://raw.githubusercontent.com/postmodern/ruby-versions/master/ruby/versions.txt

If your system has wget installed:
$ wget -c -O /Users/ppwang/.cache/ruby-install/ruby/versions.txt https://raw.githubusercontent.com/postmodern/ruby-versions/master/ruby/versions.txt

If you get an error message from the curl/wget command, then the problem is related to the network, SSL, or possibly disk space. If the command works, and the problem persists with ruby-install, then please report it to ruby-install.


[Bug]: Helm upgrade fails because the databases already exists (zitadel-setup)

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[ ] I have joined the ZITADEL chat

Version
7.3.0
App version
No response
Describe the problem caused by this bug
I'm trying to upgrade from chart 7.3.0 to 7.5.0 but unable due to zitadel-setup trying to create the database again, despite it existing already.
To reproduce

Deploy Chart 7.3.0 with Postres
Try to upgrade to chart 7.5.0 without making changes to anything
See it fail the zitadel-setup, and see the actual problem in Postgres logs.

Logs
zitadel-setup:
time="2024-01-26T10:11:42Z" level=info msg="setup started" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:67"
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=14_events_push
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=01_tables
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=02_assets
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=03_default_instance
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=05_last_failed
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=06_resource_owner_columns
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=07_logstore
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=08_auth_token_indexes
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=12_auth_users_otp_columns
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=13_fix_quota_constraints
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=15_current_projection_state
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=16_unique_constraint_lower
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=17_add_offset_col_to_current_states
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=19_add_current_sequences_index
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=config_change
time="2024-01-26T10:11:42Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:44" name=projection_tables
time="2024-01-26T10:11:42Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:11:47Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:11:53Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:11:58Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:03Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:08Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:13Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:18Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:23Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:28Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:33Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:38Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:43Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables
time="2024-01-26T10:12:48Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:136" migration step=projection_tables

Expected behavior
I would have expected it to be smart and see that it already exists, so it shouldn't try to re-create the database on upgrade but rather just run migrations if needed.
Relevant Configuration
My Helm values are here: https://github.com/samipsolutions/infra/blob/main/kubernetes/apps/security/zitadel/app/hr.yaml
Additional Context
No response

Hi @samip5
The message migration already started means that your setup step got stuck for some reason. In this case, you should run the command zitadel setup cleanup manually, so the step is retried on the next setup.
I will try to find out if there is a way to define a job in kubernetes without starting it and can be executed manually instead.


fix: input types when there is no input

this will allow doing something like:
const b = serverFn$(()=>{
  return 1;
})
b()

right now you have to pass undefined when there is no input
const b = serverFn$(()=>{
  return 1;
})
b(undefined)

changed some prettier stuff so the only actual changes are here:
https://github.com/TanStack/bling/pull/5/commits/8297859a951eb7e5d3c2af7627e33c9e0841c2e4#diff-c486f45e9fc98f16ca847f7b5f669fed1f35157df62a7edcc5f9bd40b3b9d52eR28

If you could remove semis that would be great. 😊

Oh actually, we also have some conflicts.

Moved to https://github.com/TanStack/bling/pull/6


Update compass.md

Added Experiment number 3
#60

@mariobehling @hpdang any one plz merge it

@NishithP2004 I think I have to write my experiment .
In the task it is written that I just have to write my experiment .

Your experiment contradicts experiment 2.

@NishithP2004 I think I have to write my experiment .
In the task it is written that I just have to write my experiment .

Yes, but that should not be the same thing which is already present.It should be something new.

@NishithP2004 should I do an experiment using Magent or it also present ?

Already 2 magnet related experiments are present if I'm not mistaken.
On Sun, 12 Jan 2020, 6:08 pm coder135792468<EMAIL_ADDRESS>wrote:

@NishithP2004 https://github.com/NishithP2004 should I do an experiment
using Magent or it also present ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/pslab-documentation/pull/73?email_source=notifications&email_token=AIHZ3NECRKTGBQDRBOUHUSTQ5MFL5A5CNFSM4KFXFR3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWY65A#issuecomment-573411188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIHZ3NCI7JX7VA6JQFCWOQDQ5MFL5ANCNFSM4KFXFR3A
.

@NishithP2004 the what experiment I can add ?
Should I add both magnet or wire experiment ?

Think of something ...🤔
On Sun, 12 Jan 2020, 6:47 pm coder135792468<EMAIL_ADDRESS>wrote:

@NishithP2004 https://github.com/NishithP2004 the what experiment I can
add ?
Should I add both magnet or wire experiment ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/pslab-documentation/pull/73?email_source=notifications&email_token=AIHZ3NCI3M3QQBRDAWNRQXLQ5MJ5FA5CNFSM4KFXFR3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWZYPI#issuecomment-573414461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIHZ3NG3JHK3WKUZU7ZA4R3Q5MJ5FANCNFSM4KFXFR3A
.

think of something that is not already in here


Add fractional seconds support for direct input

This PR adds fractional seconds support for direct input with nanosecond resolution.
The implementation is inspired by #2870 but:

resolution is not limited to milliseconds
fractional seconds has no extra formatting token
format resolution is controlled by formatSecondsPrecision option, any fixed digits are supported, -1 can be used for dynamic length
provides well tested implementation

allowInput (direct input modification) support is well implemented and tested for typical usecases. This PR does not aim to provide UI for setting fractional seconds via flatpickr popup in order to focus on the flatpickr internal implementation. Once this PR is merged, the UI can be easily added.
Related with:

#1361
#2520#issuecomment-912684318
https://github.com/phpmyadmin/phpmyadmin/issues/17604
https://github.com/atk4/ui/pull/2067

/cc @Aditya-ds-1806  @williamdes @chmln
Sponsored by my own company.

Hello and thank you for this improvement!
Any idea when this will be merged? The use of Flatpickr in our project will be made possible only after fractional second support has been added.

@chmln any change of merging this ?


gh-1031 - added missing import to fix accumulo 1.8 build

Codecov Report

Merging #1032 into develop will decrease coverage by 0.68%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #1032      +/-   ##
=============================================
- Coverage      62.83%   62.15%   -0.69%
+ Complexity      1183     1136      -47
=============================================
  Files            524      524
  Lines          15543    15543
  Branches        1782     1782
=============================================
- Hits            9766     9660     -106
- Misses          5009     5124     +115
+ Partials         768      759       -9

Impacted Files
Coverage Δ
Complexity Δ

...java/uk/gov/gchq/gaffer/proxystore/ProxyStore.java
0% <0%> (-69.5%)
0% <0%> (-30%)

...uk/gov/gchq/gaffer/proxystore/ProxyProperties.java
0% <0%> (-44.83%)
0% <0%> (-17%)

...hq/gaffer/hbasestore/retriever/HBaseRetriever.java
79.38% <0%> (+2.06%)
0% <0%> (ø)
:arrow_down:

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 5f2a31b...c6c656a. Read the comment docs.