Add _disable_concurrency to serialize concurrent node execution#27
Merged
sebastianrath merged 4 commits intomainfrom Feb 19, 2026
Merged
Add _disable_concurrency to serialize concurrent node execution#27sebastianrath merged 4 commits intomainfrom
sebastianrath merged 4 commits intomainfrom
Conversation
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.
This PR adds a per-node
_disable_concurrencyflag that, when set to true in a nodes YAML inputs, serializes concurrent calls to that nodesExecuteImplthrough a per-node-ID mutex.This is helpful since I noticed a few GitHub Action nodes, eg the sbom-attestation node fails because it doesn't work well if run simultaneously for x64 and arm64. The flag is stored directly on the node instance during graph loading and checked at dispatch time in the execution engine.