-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
fix: fixes sentry errors on 404's pages #6144
Merged
Merged
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ovflowd
force-pushed
the
meta/test-removing-try/catch
branch
from
November 27, 2023 12:04
0792392
to
de2e84f
Compare
ovflowd
changed the title
experiment: attempt to use .catch instead of try/catch
fix: fixes sentry errors on 404's pages
Nov 27, 2023
ovflowd
added
bug
infrastructure
Issues/PRs related to the Repository Infra
github_actions:pull-request
Trigger Pull Request Checks
labels
Nov 27, 2023
github-actions
bot
removed
the
github_actions:pull-request
Trigger Pull Request Checks
label
Nov 27, 2023
Lighthouse Results
|
AugustinMauroy
approved these changes
Nov 27, 2023
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.
SGTM
good found for next-int patch
Actually, I forgot these changes there. I should remove the patch. |
ovflowd
force-pushed
the
meta/test-removing-try/catch
branch
2 times, most recently
from
November 27, 2023 20:36
331d328
to
35a4e02
Compare
aymen94
approved these changes
Nov 28, 2023
github-actions
bot
removed
the
github_actions:pull-request
Trigger Pull Request Checks
label
Nov 29, 2023
ovflowd
force-pushed
the
meta/test-removing-try/catch
branch
from
November 29, 2023 17:48
35a4e02
to
6dcdd51
Compare
github-actions
bot
removed
the
github_actions:pull-request
Trigger Pull Request Checks
label
Nov 29, 2023
github-actions
bot
removed
the
github_actions:pull-request
Trigger Pull Request Checks
label
Nov 29, 2023
github-actions
bot
removed
the
github_actions:pull-request
Trigger Pull Request Checks
label
Nov 29, 2023
github-actions
bot
removed
the
github_actions:pull-request
Trigger Pull Request Checks
label
Nov 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR fixes our Sentry's Server Component Errors fro
/[locale]/
by making the Not Found Page client-only.This PR also removes the CPU Profiling Sentry Extension as it was mostly not being used.
The Sentry issue (internally) is: https://nodejs-org.sentry.io/issues/4614002695/events/ae345ce869cb4a7582e925bc7d1958be/
Validation
Deploy this branch preview and analyse on Sentry releases tab (https://nodejs-org.sentry.io/releases/?project=4506191307735040&statsPeriod=1h) that this issue is indeed not re-ocurring.
Related Issues
use
amannn/next-intl#614