bootloader: expose run_chain for a scoped, ordered bootloader chain - #132
Merged
Merged
Conversation
…isites The orchestrator could only run every discovered bootloader, so a caller that brings a module online after boot (Keeper's hub install) had no way to run that module's bootloaders through the boot path: it would either re-run every bootloader in the application, including ones that establish per-runtime state, or reimplement the dependency checks and status handling. run_chain(entries, options, satisfied) executes the given entries in order with the same dependency checks, result handling and stop-on-error as the boot chain, and treats the satisfied ids as completed prerequisites. run is run_chain over every discovered bootloader with nothing satisfied. Claude-Session: https://claude.ai/code/session_01UeA2CxtcVk8swzNXXi6KHu
Merged
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.
Splits
bootloader.runinto discovery plusrun_chain(entries, options, satisfied), so a caller can run a subset of bootloaders in declared order with prerequisites it already satisfied. Dependency checks, status handling and stop-on-error are unchanged. Keeper uses it to run only the bootloaders of modules a hub install changed (wippyai/keeper#87), without re-running boot-only chains such as dataflow's overseer epoch.Tests: 4 new chain tests (failed before: attempt to call a non-function), suite 19/19, lint clean.
https://claude.ai/code/session_01UeA2CxtcVk8swzNXXi6KHu