-
Notifications
You must be signed in to change notification settings - Fork 3.3k
internal: (studio) when errors occur in development, log them and do not throw and do not send to Sentry #31614
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
Conversation
… throw and do not send to Sentry
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.
Pull Request Overview
This PR updates the error handling behavior for studio errors in development by logging errors instead of throwing them or sending them to Sentry.
- Adjusts error handling conditions to log errors when not in production
- Replaces throwing errors with console error logging in development
Comments suppressed due to low confidence (1)
packages/server/lib/cloud/api/studio/report_studio_error.ts:38
- The comment on line 38 is now outdated since the error is logged instead of being thrown in development. Consider updating the comment to accurately describe the new error handling behavior.
// When developing locally, we want to throw the error so we can see it in the console
cypress
|
Project |
cypress
|
Branch Review |
ryanm/chore/do-not-throw-on-errors
|
Run status |
|
Run duration | 18m 36s |
Commit |
|
Committer | Ryan Manuel |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
12
|
|
1232
|
|
0
|
|
32150
|
View all changes introduced in this branch ↗︎ |
Warning
Partial Report: The results for the Application Quality reports may be incomplete.
UI Coverage
46.87%
|
|
---|---|
|
173
|
|
157
|
Accessibility
92.67%
|
|
---|---|
|
3 critical
8 serious
2 moderate
2 minor
|
|
886
|
… throw and do not send to Sentry
… throw and do not send to Sentry
…elopment, log them and do not throw and do not send to Sentry (#31614)
…opment, log them and do not throw and do not send to Sentry (#31614)
…elopment, log them and do not throw and do not send to Sentry (#31614)
…opment, log them and do not throw and do not send to Sentry (#31614)
…elopment, log them and do not throw and do not send to Sentry (#31614)
…opment, log them and do not throw and do not send to Sentry (#31614)
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Additional details
When studio errors occur in development, log them and do not throw and do not send to Sentry
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?