Repository navigation
feat: target settings for Python nodes and providers, and statement summaries for sqb test - #1522
Merged
chio-labs-delivery[bot] merged 22 commits intoNov 16, 2026
Conversation
…hook contexts Python side only; the native construction is not written yet.
At concurrency 1, an error that escapes a node's execution, such as a worker report the control API rejects or a run cancellation raised from the node-start report, stops the build. Above concurrency 1 the worker wrapper turned the same error into a failed model result, so the build went on starting later nodes, including after the server had rejected the run's state. Concurrent workers now pass the escaped error back to the scheduler, which stops dispatching, lets the nodes already running finish, and raises the error as the serial path does.
…ctly The failure builder only forwarded its arguments, so passing the dataclass keeps the runtime package within its code-line cap.
…loader contexts Build, check and load resolve TargetSettings once from the target they run against: database and schema as models resolve them, None with a preserved flag for preserve, and the schema a managed source without its own loads into.
TargetSettings is now a native record built from Rust values, so command structs hold no new Python objects. debug, diff and load share one effective_target_namespace that resolves the connection and adapter defaults, replacing the keyword-built pyfunction each repeated.
… feat/target-settings-and-statement-summary
…eat/target-settings-and-statement-summary
…the statement history read
…and-statement-summary # Conflicts: # crates/sqlbuild-python/src/bindings/_helpers/build_command/command.rs # crates/sqlbuild-python/src/bindings/_helpers/build_command/lifecycle.rs
The pass/fail summary and failures are written and flushed first, so a slow or interrupted warehouse history read cannot delay or hide them.
…and-statement-summary
…nts sections Both sqb test --json sections are now added by sqlbuild-core's json with_section. The Python bindings cap follows the smaller crate.
chio-labs-delivery
Bot
deleted the
feat/target-settings-and-statement-summary
branch
November 16, 2026 20:13
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
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.
Why
Python tasks, loaders, checks and providers could not see which target a command runs against.
sqb testandsqb scenario testgave no view of how many warehouse statements a run issued or how long the warehouse spent compiling them.Changes
ctx.target_config(aTargetSettingsrecord) in build, check and load.loader_schemaisNonewhen the target schema uses${CTX:...}.setup(ctx)getsProviderSetupContext(target_config=...)in build, check and load. Event exporters and orchestration sensors and calendars still pass none; the providers page says so.sqb testandsqb scenario testprint a statement summary (counts by kind; on Snowflake, compile and execution time from query history) after the results, and addstatementsto--json. The history read uses its own connection with login, network and statement timeouts; interrupts propagate; other failures print "compile time unavailable".sqb test, scenarios; skill regenerated.--sinceandstatementsJSON sections now share one helper.Out of scope: a Python task or loader in
sqb buildwith a${CTX:...}target schema still tries to create the literal templated schema in the result store. Pre-existing on main; tracked separately.Verification
-D warnings; fensu clean.make check-cipasses on the final head.DuckShop: no edge case; a CTX-templated target schema and the provider setup context are target configuration and command behaviour, not a model, macro or data shape.