-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
feat(dashboards): POC for sharing dashboards #82455
base: master
Are you sure you want to change the base?
Conversation
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
except Organization.DoesNotExist: | ||
return Response({"detail": "Organization not found"}, status=404) | ||
except Exception as e: | ||
return Response({"error": str(e)}, status=400) |
Check warning
Code scanning / CodeQL
Information exposure through an exception Medium
Stack trace information
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix AI 22 days ago
To fix the problem, we should log the detailed exception message on the server and return a generic error message to the user. This approach ensures that sensitive information is not exposed to the user while still allowing developers to access the necessary details for debugging.
- Modify the exception handling block to log the exception message and stack trace.
- Return a generic error message to the user instead of the actual exception message.
-
Copy modified lines R95-R96
@@ -94,3 +94,4 @@ | ||
except Exception as e: | ||
return Response({"error": str(e)}, status=400) | ||
self.logger.error("An error occurred: %s", str(e), exc_info=True) | ||
return Response({"error": "An internal error has occurred."}, status=400) | ||
|
❌ 8 Tests Failed:
View the top 3 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you add the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
DRAFT: POC for sharing dashboards