Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

e2e: Spew ODataError details before panicing #3265

Merged
merged 1 commit into from
Nov 9, 2023

Conversation

mbarnes
Copy link
Contributor

@mbarnes mbarnes commented Nov 7, 2023

Which issue this PR addresses:

Errors returned from MS Graph APIs are useless as an error type. They just use a hard-coded message:

error status code received from the API

To get to the real information requires casting the error as an ODataError and unpacking the details, which I usually just "spew" to a log.

This is to help debug such errors we're currently seeing in E2E tests.

@SudoBrendan
Copy link
Collaborator

Hah - so, if E2E fails and showcases the new functionality, is that ❌ actually a ✔️ ? 😂

@SudoBrendan
Copy link
Collaborator

/azp run e2e

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mbarnes
Copy link
Contributor Author

mbarnes commented Nov 8, 2023

Rebased on master after #3269 merged, which will hopefully fix E2E.

@bennerv bennerv merged commit d0c6db7 into Azure:master Nov 9, 2023
18 checks passed
@mbarnes mbarnes deleted the e2e-msgraph-errors branch November 9, 2023 17:19
ventifus pushed a commit to ventifus/ARO-RP that referenced this pull request Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants