Repository navigation
fix(orchestration): claim sources loaded through hook reads and loader chains - #1446
Merged
Merged
Conversation
…r chains Snapshots record `loads` on models (managed sources their hooks or audit gates read beyond `deps`) and on managed sources (the declared sources in their loader chain), additive and absent when empty. A job's write set claims a selected model's `loads` and each loaded source's chain, so the worker no longer refuses those runs. A directly selected source claims only itself, as only its own loader runs. An intermediate loader that no source declares stays unclaimed, so runs that need one still fail in the worker. Models and sources that gain `loads` show as changed once, on the first publication after upgrading.
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 13, 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 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
A job's frozen write set missed two kinds of source a build loads: managed sources a model's hooks read, and the sources in a loaded source's loader
depends_onchain. The worker refused those runs withplanned writer source:… is outside the frozen run write set.Changes
loadson a model (managed sources its hooks or audit gates read beyonddeps) and on a managed source (the declared sources in its loader chain). The field is additive and absent when empty.loadsand each loaded source's chain. A directly selected source claims only itself, as only its own loader runs;--no-load-sourcesclaims none.loadsshow as changed once, on the first publication after upgrading.Verification
loadsthe hook-read source is refused; an intermediate loader is refused.node_loadsunit test; orchestration crate on SQLite and PostgreSQL, incl. a selected source claiming only itself.make check-ci.edge_cases/orchestration/loaded_*andintermediate_loader_*.