-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Preserve the original error name instead of returning raw AbortError #57550
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
Preserve the original error name instead of returning raw AbortError #57550
Conversation
|
Pinging @elastic/kibana-platform (Team:Platform) |
|
@lukasolson @kobelb does this need to be backported to |
|
retest |
|
@pgayvallet No, 7.7 should be fine. |
kobelb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - this fixes the error that the Security plugins response error interceptor was previously throwing. Thanks @pgayvallet!
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
…lastic#57550) * Preserve the original error name instead of returning raw AbortError * use Error as the default error name
|
@lukasolson This one should be trivial to backport to 7.6.1. Not sure about #55061 though. @restrry ? |
…lastic#57550) * Preserve the original error name instead of returning raw AbortError * use Error as the default error name
Summary
Fix #56244
nameattribute toHttpFetchErrorand initialize it with the underlying errorAbortErroras a special case infetchResponseChecklist
For maintainers