-
Notifications
You must be signed in to change notification settings - Fork 27
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
♻️ aiohttp
deprecation: Using web.json_response
to return 2XX
responses instead of raising HttpException
#6829
Conversation
aiohttp
deprecation: Using web.json_response
to return 2XX
responses instead of raising HttpException
services/storage/src/simcore_service_storage/handlers_simcore_s3.py
Outdated
Show resolved
Hide resolved
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6829 +/- ##
==========================================
- Coverage 88.14% 88.14% -0.01%
==========================================
Files 1513 1513
Lines 59634 59632 -2
Branches 2166 2166
==========================================
- Hits 52562 52560 -2
Misses 6741 6741
Partials 331 331
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
d56a6cd
to
9ae6010
Compare
71a24d8
to
966110a
Compare
Quality Gate passedIssues Measures |
What do these changes do?
aiohttp
deprecated returningHttpException
. Moreover, raising non-error creates false negatives as in the example below where201
(Created) was shown as an error in our tracingJaeger captures these exceptions as errors in storage:
Related issue/s
aiohttp
deprecation: Usingweb.json_response
to return2XX
responses instead of raisingHttpException
#6563How to test
Dev-ops
None