Conversation
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2633 +/- ##
=======================================
Coverage 79.08% 79.08%
=======================================
Files 661 661
Lines 51990 51989 -1
Branches 732 732
=======================================
Hits 41114 41114
+ Misses 10796 10795 -1
Partials 80 80
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
mcosgriff
left a comment
There was a problem hiding this comment.
Would it be beneficial to instead return an object that can be serialized to the front-end, that way the message is what's displayed by default but the user can get the whole stack trace without looking into the log files?
|
Perhaps but we have to match the behavior in both the Ruby and the Python. For now let's merge and fix this bug. |
We updated the Python logging to do full stack traces. This caused the frontend to display this ugly stack trace. We're still logging the full stack error but the frontend should only get the message.
Before:
After: