-
Notifications
You must be signed in to change notification settings - Fork 32
🎨 Improves webserver's exception handling to enhance diagnoses of catalog's client errors #7817
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
🎨 Improves webserver's exception handling to enhance diagnoses of catalog's client errors #7817
Conversation
… response mapping
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7817 +/- ##
==========================================
- Coverage 85.80% 82.58% -3.22%
==========================================
Files 1850 703 -1147
Lines 71910 33579 -38331
Branches 1218 176 -1042
==========================================
- Hits 61700 27732 -33968
+ Misses 9868 5789 -4079
+ Partials 342 58 -284
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
matusdrobuliak66
left a comment
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.
👍



What do these changes do?
This PR refines the error handling logic using
catalog._cotnroller_rest_excetpions._handler_catalog_client_errorsto log detail troubleshooting information for diagnostics while keeping (for now), the current behavior:404, the webserver REST API returns a404.503by the webserver REST APIIMO the current logic is overly coarse—many
4XXerrors may indicate client-side issues rather than catalog unavailability, but we will wait until we see the errors to enhance that.Related issue/s
How to test
Dev-ops