Distinguish Query API wake delays from gateway execution timeouts - #958
Merged
Merged
Conversation
sdairs
added this pull request to stack #876
September 15, 2026 15:49
sdairs
marked this pull request as ready for review
September 16, 2026 13:14
Carry existing lower-stack README corrections and ancestry forward. The merged tree matches the independently verified cumulative stack result.
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
2 participants
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.
A Query API timeout can occur while an idle service wakes. Use the existing typed service state and an explicit pre-execution idle response to suggest a state check when waking is plausible. Otherwise retain native-client guidance. Both paths explain that SQL may have executed, preserve the
query_timeoutcode and telemetry, and never retry an ambiguous timeout.Validation
97 query subprocess tests passed (1 ignored), timeout telemetry matrix and existing provisioning-stage tests passed, default CLI clippy passed. The complete integrated validation is recorded below.
Closes #826
Appended to native GitHub stack #876.
Combined local validation
Combined stack head
e20d63b3af4c8541a6f597d9494b530f2c56b666passed all required local checks: formatting, CLI clippy/tests, telemetry-disabled check and all-target clippy, API/analyzer all-target clippy/tests, all-feature workspace build, Python classifier/drift tests, and diff checks.Test totals: 1991 CLI, 672 API/analyzer, and 93 Python tests (2756 total). Ignored/live tests are excluded from these totals.
Snapshot API access was revalidated successfully on the exact heads of PRs #940 and #944 after the environment feature flag was enabled. Run links and coverage details are recorded in tracker #939.
Stack order, exact heads and explicit issue Development relationships were verified in the implementation tracker.