This repository was archived by the owner on Nov 8, 2026. It is now read-only.
Repository navigation
Let callers control Scan deadlines - #24
Merged
Merged
Conversation
This was referenced Sep 19, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Scan now honors the caller context without adding a default 30-second deadline. Applications can still opt into a whole-page limit through
ClientOptions.ScanTimeout; admission retries remain bounded by their attempt policy.Validated with the full unit/race suite and public integration tests against the matching Gateway/Engine/Worker candidate. Includes regression coverage for absent deadlines and caller-selected long deadlines.