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

hotfix(dashboard): occasional 500 errors #940

Merged
merged 1 commit into from
Dec 15, 2023

Conversation

IGassmann
Copy link
Contributor

Description

500 errors were sporadically happening on the Dashboard during a page load.

The errors started to happen since #817 was merged, which updated Next.js, Sentry, and Clerk:

image

The issue was recently identified by the Vercel team as coming from the Sentry package: https://github.com/orgs/vercel/discussions/3248#discussioncomment-7851868 and was recently fixed by Sentry: getsentry/sentry-javascript#9811

Type of change (choose one)

  • Chore (refactors, upgrades, etc.)
  • Bug fix (non-breaking change that fixes an issue)
  • Security fix (non-breaking change that fixes a potential vulnerability)
  • Docs
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality not to work as expected)

Checklist

  • I've linked any associated issues to this PR.
  • I've tested my own changes.

Check our Pull Request Guidelines

Copy link

vercel bot commented Dec 15, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
ui ✅ Ready (Inspect) Visit Preview Dec 15, 2023 11:12am

@IGassmann IGassmann enabled auto-merge (squash) December 15, 2023 11:12
@IGassmann IGassmann merged commit 9205f86 into main Dec 15, 2023
9 of 10 checks passed
@IGassmann IGassmann deleted the igor/500-errors-due-to-sentry branch December 15, 2023 11:13
Copy link
Member

@djfarrelly djfarrelly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad that we were able to find the source of this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants