-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
chore: don't log server errors for aborted requests #5602
Conversation
🦋 Changeset detectedLatest commit: 71f1a8f The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -383,10 +389,6 @@ async function errorBoundaryError(error: Error, status: number) { | |||
} | |||
|
|||
function returnLastResortErrorResponse(error: any, serverMode?: ServerMode) { | |||
if (serverMode !== ServerMode.Test) { | |||
console.error(error); | |||
} |
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.
Moved the log to a utility that does the checking and lifted to the 2 places we call returnLastResortErrorResponse
🤖 Hello there, We just published version Thanks! |
Since aborted requests is an ecpedted flow, we should not log the error from the router (i.e.,
new Error("queryRoute() call aborted")
). We had this check for some flows but not all.