-
Notifications
You must be signed in to change notification settings - Fork 364
server: load initial source asynchronously so /api/ping is responsive immediately #2829
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
Closed
+143
−12
Closed
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
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.
[MEDIUM] Non-deterministic
Readresult when context is already cancelled after initial loadWhen the
readychannel is already closed (initial load complete) and the caller'sctxis already done, bothselectcases are simultaneously ready and Go picks one at random (~50/50). This means a caller with a cancelled request context can receive(nil, context.Canceled)even though valid cached data sits insl.data.The previous implementation declared
Read(_ context.Context)— the context was fully discarded, so cancelled contexts never caused data-access failures. This PR changes that contract: a request context cancelled just after the initial load completes (e.g. a slow client dropping its HTTP connection) will now non-deterministically return an error instead of the cached data.Minimal fix — check
readyfirst with a non-blocking select, and only then honour context cancellation:This preserves the blocking-until-loaded contract while never sacrificing already-cached data to a racing cancellation.