fix(opencode): enhance error aggregation to surface named errors with structured fields#27057
Draft
OpeOginni wants to merge 3 commits into
Draft
fix(opencode): enhance error aggregation to surface named errors with structured fields#27057OpeOginni wants to merge 3 commits into
OpeOginni wants to merge 3 commits into
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.
Issue for this PR
Closes #27056
Type of change
What does this PR do?
aggregateFailures now detects when all parallel bootstrap failures share the same named error (e.g. ConfigInvalidError). If every failed request rejected with the same named error, it returns that single structured error as an Error instance with name and data attached, so FormatError can render the proper human-readable config message. If the failures are mixed, it falls back to the existing aggregated "X of Y requests failed: ..." message.
How did you verify your code works?
Tested with the dev instance and added regression tests ensuring all pass.
Screenshots / recordings
Checklist