fix(cron): cap job toolsets by config - #25937
Closed
Osraka wants to merge 1 commit into
Closed
Conversation
Collaborator
Contributor
Author
|
Closing this as a duplicate of the earlier fixes for #25752 (#25780, #25786, #25815, #25842). I missed the existing work before opening this; apologies for the extra noise.\n\nThe main behavior I wanted to preserve here is that a fully denied per-job override should remain an explicit empty toolset rather than falling back to the default toolset set. That concern is already being discussed on the earlier PRs, so I will follow the existing thread instead of keeping another competing fix open. |
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.
Summary
Fixes #25752
Tests
Note: scripts/run_tests.sh could not run locally because this checkout has no .venv or venv; the equivalent pytest commands above passed.