Repository navigation
Check cubby targets before executing jobs - #111
Merged
Merged
Conversation
plotnick
force-pushed
the
own-cubby
branch
2 times, most recently
from
November 4, 2026 16:37
b72035f to
ac27d2b
Compare
Co-authored-by: Claude <noreply@anthropic.com>
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.
Follow-up to #104. As of that PR, when a sled accepts a job it attaches a list of sleds that it believes should run a job. But that list isn't signed, so to avoid even potentially running a job on an incorrectly targeted sled, this PR makes each sled check its own baseboard and cubby against the signed target list in the original request before executing a job (like other such gossiped evidence). Also took the opportunity to clean up some of the target and job pre-flight checks.