Actions
Bug #42565
closedmgr/dashboard: "TypeError: Object of Type LazyUUID4 is not JSON serializable"
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
After Debug mode PR was added, now when an exception is triggered, the error responses from the back-end include a UUID of the request (in order to better match HTTP responses and log traces). In older versions of Cherrypy (like the ones most distros come with), this UUID is not yet implemented, so Debug mode had to provide a work-around for this. That's why there are 2 different implementations for the UUID: the work-around one works, while the native one doesn't. It triggers another exception because of an error when JSON serializing the response.
In order to avoid different code paths for older-newer versions, I'll basically include the same implementation for both.
Files
Updated by Ernesto Puerta over 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 31266
Updated by Ernesto Puerta over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 146 to General - Back-end
Actions