fix: first chain/region tab rendered aggregate data - #416
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.
page.tsx pre-seeded the variant map's initially-selected chain/region/kind key with the AGGREGATE benchmark, so the client never fetched the real variant for that combo: ?chain=bnb on metadata-coverage / aggregator-head-lag and the first region on rpc-capabilities silently showed global data labeled as filtered (identical charts across chains, dRPC ranked first on every region). Verified the variant API itself returns correct distinct data (mobula head-lag: 1207ms bnb vs 15ms solana). Only the unfiltered key is seeded now; the real variant loads on demand with the aggregate as placeholder.