Skip to content

fix(spec): dedupe results after legacy chain slug rewrite - #767

Merged
Flotapponnier merged 1 commit into
devfrom
fix/dedupe-aliased-chain-results
Jun 27, 2026
Merged

fix(spec): dedupe results after legacy chain slug rewrite#767
Flotapponnier merged 1 commit into
devfrom
fix/dedupe-aliased-chain-results

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

When a chain rename rolls through Prom while the 24h window still holds samples on the legacy label (e.g. ton → gram during harness redeploy lag), the loader rewrote each ton row to gram but did not dedupe → /benchmarks/l1-finality rendered Gram twice (one row per source series). Two-pass: rewrite then dedupe by canonical slug, preferring the row whose original slug already matched the canonical.

When a chain rename rolls through Prom while the 24h window still holds samples on the legacy label (e.g. ton → gram during the harness redeploy lag), the loader rewrote each ton row to gram but did not dedupe — so /benchmarks/l1-finality rendered Gram twice (one row per source series).
Two-pass: rewrite then dedupe by canonical slug, preferring the row whose original slug already matched the canonical (current harness emit) over the alias-rewritten historical row.
@Flotapponnier
Flotapponnier merged commit a3fcafa into devJun 27, 2026
1 check passed
@Flotapponnier
Flotapponnier deleted the fix/dedupe-aliased-chain-results branch June 27, 2026 21:38
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@Flotapponnier