fix: prevent duplicate running status requests#175
Merged
Conversation
cxymds
marked this pull request as ready for review
July 21, 2026 01:09
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.
Pull Request
Description
Prevent the Running Status page from issuing an initial request batch that is immediately canceled and repeated.
The duplicate traffic had two causes:
The API client now remains stable across dashboard navigation while the 403 handler reads the latest pathname through a ref. Initial status and admin requests are deferred to a cancelable microtask so Strict Mode preview effects do not reach the network.
Type of Change
Testing
pnpm install --frozen-lockfile pnpm tsc --noEmit pnpm lint pnpm prettier --check . pnpm test:run git diff --checkAll 338 tests pass.
Checklist
Related Issues
N/A
Screenshots (if applicable)
N/A — request lifecycle behavior only; no visual changes.
Additional Notes
The existing timeout, refresh interval, visibility refresh, request abort, and stale-response protection behavior remains unchanged.