fix: curated compare pairs indexable again + freshness store fallback - #1109
Merged
Conversation
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.
The curated exemption keyed on the optional benchmarks override, which no curated entry sets: usdc-vs-usdt, dydx-vs-hyperliquid and ethereum-vs-solana were serving noindex on prod while listed in the sitemap. Curation is now COMPARE_PAIRS membership. Also /api/freshness returned an empty map since launch on prod (Prom unreachable from Vercel): it now falls back to the materialized store lastRunAt per bench, Prom keeps priority when reachable.