Repository navigation
Refresh status immediately on manual request - #5
Merged
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
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.
Make the Refresh button request the latest status immediately. Previously, clicking it before the configured polling interval elapsed returned cached data, and minute-only timestamps made the button appear ineffective.
Manual refresh now bypasses both the configured automatic interval and automatic retry backoff. The popup disables the button while the request is running, confirms success or failure in an accessible status message, and displays the successful update time with seconds. Failed requests retain the last successful timestamp and cached data.
Only an explicit provider Retry-After defers manual requests, with an explanation and countdown. Concurrent requests share one fetch; a manual click that joins an automatic cache-only check still starts a real request. Automatic polling continues to use the configured interval and backoff.
Validation: TypeScript build/typecheck, formatting, 17 unit tests, 12 real Chromium scenarios, release packaging tests, ZIP packaging, and diff checks passed. Browser tests cover fresh-cache manual refresh, immediate consecutive clicks, retry after network recovery, Retry-After, concurrent callers, and a manual click racing an automatic cache check.