Fix dag parsing persistence when bundle cache is missing after processor restart#69972
Open
GayathriSrividya wants to merge 1 commit into
Open
Conversation
GayathriSrividya
requested review from
ephraimbuddy and
jedcunningham
as code owners
July 16, 2026 13:48
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.
closes #69249
What this PR changes
Why this fixes the issue
After a dag-processor restart, parsing can proceed before _bundle_versions is populated for a bundle. The previous direct index access raised KeyError, which short-circuited persistence and prevented normal DAG metadata updates. Falling back to None keeps persistence moving and allows stale DAG state to be refreshed instead of remaining stuck.
Tests