Repository navigation
Enforce cooperative SQL deadlines and release flyquery 26.10.3 - #10
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
1 participant
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 configured statement timeout previously left DuckDB running until it finished. Each execution attempt now has a monotonic budget and native interruption, and expired statements are recorded as
FAILEDwith SQL state57014. Critic does not repair a timed-out statement or restore an earlier success after a repair timeout.Cancellation waits for the attempt's own worker and connection to close. Copy-on-write cleanup removes its scratch file even if native close reports a failure, preserves the original snapshot, and keeps cleanup failure chained to cancellation. This is cooperative interruption per attempt, not a hard process kill or a total model/retrieval/storage SLA. Existing finite candidate policy remains unchanged.
Server, Python SDK and Java SDK metadata advance to 26.10.3. All 400 metadata paths normalize exactly to the independently reviewed runtime source; generated methods, DTOs, authority and OpenAPI bodies remain unchanged. Existing framework pins and 19 historical plus 2 reviewed source variants are preserved. Operational guides now explain the implemented timeout and its limits.
Validation: 467 units; 111 native integrations (15 optional storage skips, 1 paid-model deselection); 12 dedicated native deadline/cancellation/cleanup probes; Ruff/format; types: 0 errors and 12 existing warnings; 25 SDK source tests and 25 tests against a fresh installed wheel; seven actual typed Python and Java SDK GETs against the retained installed 26.10.2 service; Java 25 Maven verify: 857 tests, 135 generated skips and 0 failures. No paid models or cloud deployment. The SDK compatibility proof is separate from installed 26.10.3 server acceptance.