ERA-13244: Fix HTTP errors showing "unknown error" instead of human-readable message on event submit#1561
Open
jeslefcourt wants to merge 5 commits into
Open
ERA-13244: Fix HTTP errors showing "unknown error" instead of human-readable message on event submit#1561jeslefcourt wants to merge 5 commits into
jeslefcourt wants to merge 5 commits into
Conversation
…-13244) Fixes generateErrorMessageForRequest checking error.response?.status?.code (always undefined on an Axios number status) instead of error.response?.status, and updates the ReportDetailView error catch block to use it so 429 and other HTTP errors show their localized message instead of "unknown error". Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…Details generateErrorMessageForRequest crashes when called with undefined (e.g. when Promise.reject() is called with no value). Guard with a null check before calling it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
luixlive
requested changes
May 22, 2026
luixlive
left a comment
luixlive
left a comment
Contributor
There was a problem hiding this comment.
Trivial and sound. I just think we need to double check if that change in generateErrorMessageForRequest is correct.
… surfaces generateErrorMessageForRequest checked error.request before the error.response.status switch. Axios errors that received an HTTP response (e.g. 429) carry both .request and .response, so the early return short- circuited to 'noResponse' and the status switch — including case 429 — was never reached. Reorder response-status first, then the no-response check. Add request.test.js (covers 429, other statuses, no-response, the both-set axios shape, and no-code) and a ReportDetailView test for the catch path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Address review feedback (luixlive): the status code may live at error.response.data.status.code (DAS error body), error.response.status.code (status object), or error.response.status (numeric HTTP status). Read all three with body-first precedence so the human-readable message (e.g. 429 "too many requests") surfaces regardless of shape. Expand request.test.js to 11 cases covering each shape plus body-code precedence over numeric status. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…error-message # Conflicts: # src/ReportManager/ReportDetailView/index.js
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
generateErrorMessageForRequestinsrc/utils/request.jswhich was checkingerror.response?.status?.code— Axios puts the HTTP status code aterror.response.status(a number), so.codewas alwaysundefinedand the switch never matched any casegenerateErrorListForApiResponseDetailscatch block inReportDetailViewto callgenerateErrorMessageForRequestinstead of always falling back to "unknown error"Test plan
Jira: ERA-13244
🤖 Generated with Claude Code