Conversation
Discusses how lineage entries could be used to detect and explain cache misses, by diffing two lineage TaskRun records. Records the options for producing, versioning and exposing the list of record fields that feed the task hash, together with the drift between TaskHasher and the lineage record that has to be fixed under any of them. Status is draft: no option is selected yet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: jorgee <jorge.ejarque@seqera.io>
✅ Deploy Preview for nextflow-docs canceled.
|
jorgee
marked this pull request as draft
September 14, 2026 12:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an ADR discussing how lineage entries could be used to detect and explain cache misses.
Seqera Platform wants to answer "why was this task not cached?" by diffing two lineage
TaskRunrecords. That only works if the consumer knows which fields of the record actually feed the task hash, and that set changes over time. The ADR records the options for producing, versioning and exposing that field list, together with the drift betweenTaskHasherand the lineage record that has to be fixed under any of them.Status is draft — no option is selected yet.
🤖 Generated with Claude Code