hotfix: register cosmos-hub chain (unblocks prod smoke) - #1268
Merged
Conversation
…ducts/ (unblocks smoke)
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
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.
Why
Prod deploy has been auto-rolling back for 24h. Latest smoke run (474653e) fails on:
The validator-yield bench declares `cosmos-hub` as a result slug, so `buildProviders()` creates a profile for it → sitemap advertises `/products/cosmos-hub`. But `getProvider("cosmos-hub")` on the page path can return undefined mid-render (the appearance sourcing race also seen with quicknode/coingecko/infura before), so smoke sees a 404 and rolls the deploy back.
Fix
Add `cosmos-hub` to `CHAIN_BY_SLUG` (same registry that already carries sui, cardano, avalanche, etc. from the same bench). Two effects:
Same pattern used for every other chain-slug that appears as a validator-yield result.
Blocked by this getting to prod