Skip to content
This repository was archived by the owner on Jan 12, 2024. It is now read-only.

Conversation

@ricardo-espinoza
Copy link
Contributor

Extending the message in WorkspaceClientException to include the inner exception as well if present.

This exception message is provided to the user through the console during execution (e.g. when using the Azure CLI) and should include this information to be more actionable.

@ricardo-espinoza ricardo-espinoza merged commit 9207633 into main Sep 17, 2020
@ricardo-espinoza ricardo-espinoza deleted the ricardoe/bugs/output-inner-exception branch September 17, 2020 17:32
ricardo-espinoza added a commit that referenced this pull request Sep 23, 2020
…ionable information (#380)

Improving the logging of WorkspaceClientException to include more informative data in its message from its inner exception. This is a follow up to #378 .

- Instead of providing the full stack of the exception in the output, we extract more relevant fields from the source RestErrorException and provide them to the user.
- Also, this change exposes header "x-ms-request-id"if present in the response, for additional debugging.
cgranade pushed a commit that referenced this pull request Sep 23, 2020
…ionable information (#380) (#386)

Improving the logging of WorkspaceClientException to include more informative data in its message from its inner exception. This is a follow up to #378 .

- Instead of providing the full stack of the exception in the output, we extract more relevant fields from the source RestErrorException and provide them to the user.
- Also, this change exposes header "x-ms-request-id"if present in the response, for additional debugging.

Co-authored-by: Ricardo Espinoza <ricardoe@microsoft.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants