feat: add orchestration engine for GraphGen and tests #85
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
…to feature/orchestration-operation
…to feature/orchestration-operation
31 tasks
CHERRY-ui8
pushed a commit
to CHERRY-ui8/GraphGen
that referenced
this pull request
Dec 17, 2025
…estration-operation feat: add orchestration engine for GraphGen and tests
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.
This PR adds a lightweight orchestration engine to GraphGen, turning the former hard-coded, sequential pipeline into a configurable, concurrent DAG.
Key changes:
Engine(topological sort + thread-pool execution) and@opdecorator to declare tasks and dependencies.generate.pywithrun.py; it loads the DAG from pipeline sections in YAML configs and executes it.generate()method into two atomic ops: partition and generate, letting the engine handle their dependency.