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
This new
graph.pykeeps the same DAG model and validation but restructures runtime scheduling and readability: ready queues moved from publicdequefields to internal, non-serialized structures grouped by node class, with a configurable class priority and optional batch cap;indegreeis now seeded as unmet inputs (fixing iterator stalls) and children are enqueued via a single_enqueue_if_ready()helper;next()drains the active class queue, reseeds when empty, and_prepare()still expands iterators but with clearer predicates; minor fixes include catchingValueErrorindelete_edge, replacing magic port strings withITEM_FIELD/COLLECTION_FIELD, and renaming helper methods for clarity. Functionality and performance are preserved aside from the scheduling policy change and the indegree correctness fix.Additionally, there is a new
README.mdfile that explains a bit about the classes ingraph.pyso future developers can get a head start.Related Issues / Discussions
All of this was an effort to understand the execution engine better to support different types in the future - if, loops, and the like.
QA Instructions
I've run a number of workflows with these changes and all seems good.
Merge Plan
Checklist
What's Newcopy (if doing a release after this PR)