Repository navigation
fix(app): keep Kubernetes dashboard tables on screen while the page refreshes #3228
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
Open
Harshul1484
wants to merge
2
commits into
ClickHouse:main
Choose a base branch
from
Harshul1484:fix/kubernetes-tables-refresh-pulse
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| --- | ||
| '@hyperdx/app': patch | ||
| --- | ||
|
|
||
| fix: keep Kubernetes dashboard tables on screen while the page refreshes | ||
|
|
||
| On a refresh, the Pods, Nodes and Namespaces tables dropped their rows and | ||
| showed a loading skeleton until the new range loaded. They now keep the | ||
| current rows on screen and pulse while the refetch runs, like the charts | ||
| beside them. |
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.
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.
🔵 minor —
isSameQueryIgnoringDateRangerepeatsdiffersOnlyInDateRangein useOffsetPaginatedQuery, which breaks the REQUIRED DRY rulepackages/app/src/hooks/useOffsetPaginatedQuery.tsx:66(differsOnlyInDateRange) already runs the same check:isEqual(omit(a, ['dateRange']), omit(b, ['dateRange'])). It also compares the other key parts (prefix, timeout), which the new copy skips. The new copy only asks whether some key element equals the config, so a change inenableQueryChunking,enableParallelQueries,minGranularitySecondsorqueryKeyPrefixstill keeps the stale rows. Move the check intouseQueriedChartConfigas akeepPreviousDataoption, asuseOffsetPaginatedQuerydoes for DBTableChart. The hook knows its own key layout, so each part can be compared by position instead of scanned with.some, and the three tables passkeepPreviousData: trueinstead of repeating the sameplaceholderDataclosure.Advisory. Fix if it is a small defect in code this PR changes; otherwise reply in the thread. Do not widen the PR or touch files it did not already change. How to respond
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.
Moving this into
useQueriedChartConfigas akeepPreviousDataoption would change a shared hook this PR doesn't touch, so per AGENTS.md I've kept it local; on these tables the other key parts (chunking, parallel, granularity) never change without the config changing too, and I'm happy to do the hook option as a follow-up.