Repository navigation
Distinguish invalid Dag access control from FAB backend failures - #74788
Merged
Merged
Conversation
1 task done
This was referenced Oct 15, 2026
ephraimbuddy
marked this pull request as ready for review
October 15, 2026 12:07
ephraimbuddy
force-pushed
the
dag-processor-fab-validation
branch
from
October 16, 2026 15:35
6bb9d0c to
d11b39e
Compare
vincbeck
approved these changes
Oct 19, 2026
Callers need to distinguish malformed Dag access control from permission backend failures so they can report invalid input without suppressing transient infrastructure errors. Existing FabException handlers remain compatible.
ephraimbuddy
force-pushed
the
dag-processor-fab-validation
branch
from
October 20, 2026 10:55
d11b39e to
403d678
Compare
28 of 93 tasks
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.
Report malformed Dag access-control definitions as validation errors. Backend failures keep their original exception type, allowing atomic parse publication to reject invalid metadata while retrying infrastructure failures.
Layer 1 of the seven-part replacement for #74233, in GitHub native stack #74792. Base:
main. This prerequisite can be merged independently.GitHub's Files changed tab shows this layer. Compare this layer.
Merge order:
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-6) following the guidelines