-
Notifications
You must be signed in to change notification settings - Fork 18.4k
fix(dashboard): initialize label colors before mounting charts #44557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
rusackas
merged 3 commits into
apache:master
from
deepujain:fix-40708-initial-label-colors
Sep 24, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker, just a note for the description: I think this line is the load-bearing half of the fix, and the summary currently reads as if the first-render race were the main story.
I ran both branches side by side. With
DashboardContainermounted anddashboardInfo.idchanging in place, this branch dispatchesapplyDashboardLabelsColorOnLoada second time with the newlabel_colors; on61fffbe0c0it is never dispatched again, becausedashboardLabelsColorInitiatedis alreadytrue. The effect cleanup has meanwhile runonBeforeUnload, which callsresetColors()on the namespace, so on master the second dashboard keeps palette colors for the rest of the session until a full reload. That matches the reporter'sAfter refreshing or clicking legend, the colors become correctin #40708, andsrc/pages/Dashboard/index.tsx:25rendersDashboardPagewith nokey, so in-app navigation really does swapdashboardInfo.idunder a mounted container.For the first-render half I could not build a cold-load repro:
hydrate.ts:174seeds every chart from the initialchartstate withqueriesResponse: null, andDashboardPage.tsx:423only mounts the container oncedashboardInfois populated, so no chart owns a query response at that first commit on a fresh page load. Am I missing a path there? Either way, calling the navigation case out in the description would make this easier to justify.