fix: handle AggregateError in global error handler#10
Merged
Conversation
CI runs lint, format check, tests, and build on PRs and pushes to main. Publish workflow triggers on v* tags and publishes to npm with provenance.
Azure SDK wraps retry failures in an AggregateError with an empty message, causing the CLI to print "Error:" with no details. Extract and deduplicate inner error messages instead.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
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
2 participants
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
AggregateError(e.g. after retry exhaustion on auth failures)--rulesflag, linting/formatting setup, and prior fixes (0.1.1–0.1.3)Test plan
AggregateErrorby sending to a namespace without Send claims — error now displays the actual unauthorized messagesendandimportcommands work against dev namespace