Repository navigation
flyquery 26.10.3
flyquery now interrupts each DuckDB execution attempt when its configured deadline expires. The budget covers queueing, setup, SQL, row fetching and copy-on-write export. Timed-out statements are recorded as FAILED with SQL state 57014; Critic does not repair this resource failure or restore an earlier success after a repair timeout.
Cancellation waits for the attempt's own worker and connection to close. Original snapshots remain unchanged, scratch output is removed even when native close reports a failure, and cleanup errors remain chained to cancellation. Transient interruption failures are retained and retried. Large positive integer budgets cannot overflow the watchdog's native wait.
This is a cooperative, per-attempt deadline—not a hard process kill or an end-to-end request SLA. Model calls, retrieval and object-store work outside the executor have separate budgets. Existing finite candidate policy, authorization, registered-file fences and the seven typed agent page APIs are preserved.
Python and Java SDK metadata report 26.10.3. The qualified framework pins and nineteen historical source contracts plus two reviewed variants remain unchanged. Operational guides explain the implemented behavior and its limits.
Validation: 467 unit tests; 111 native integrations (15 optional storage skips and one paid-model deselection); native interruption, cancellation and cleanup regressions; SDK source and fresh-installed-wheel tests; actual authenticated seven-page SDK reads; Java 25 Maven validation; lint, types and exact-source CI. Paid providers and cloud deployment were not used. Public artifact verification is recorded separately from local server qualification.
What's Changed
Full Changelog: v26.10.2...v26.10.3
