Skip to content

fix(console): prevent stale refreshes from overwriting fleet state - #451

Open
Maya-Kid wants to merge 1 commit into
deeplethe:devfrom
Maya-Kid:fix/console-refresh-order
Open

Maya-Kid wants to merge 1 commit into
deeplethe:devfrom
Maya-Kid:fix/console-refresh-order

Conversation

@Maya-Kid

Copy link
Copy Markdown

An overlapping refresh could replace newer fleet data with an older response. Switching away from a time range and back could also accept a response from the previous visit.

Apply each refresh to the active range and sign-in session, and discard responses older than the latest settled refresh. A slow response can still update the page while newer polls are pending. Use the same ordering for refresh errors and loading indicators.

Nine regression and control tests cover out-of-order replies, range changes, slow polling, stale errors, and loading transitions. All 21 console tests, the production build, and diff checks passed on Node 22.

Signed-off-by: dada-yan <BinjunYann@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant