-
Notifications
You must be signed in to change notification settings - Fork 310
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
Respect reraise setting #571
Conversation
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.
😄 - good catch Vidar. Just had the one comment. I was not aware of this option.
Codecov Report
@@ Coverage Diff @@
## master #571 +/- ##
==========================================
+ Coverage 77.12% 77.52% +0.40%
==========================================
Files 109 109
Lines 10115 10171 +56
Branches 1089 1096 +7
==========================================
+ Hits 7801 7885 +84
+ Misses 1929 1897 -32
- Partials 385 389 +4
Continue to review full report at Codecov.
|
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.
Great! I like having the server starting by defaullt although some extensions fail. Keeping reraise_server_extension_failures to False by default is good. Thx @vidartf for honouring a True value in this PR. |
We have this nice setting for having extension load failure raise errors instead of silently failing. We should respect it 😄
So that it can always check the reraise errors flag
Supposedly this will bring me great luck and good fortune!
52e1892
to
496dc68
Compare
Rebased now. I just had to get my antivirus to stop deadlocking pre-commit 👍 |
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.
Nice, thank you! I'll wait for @Zsailer to have a look since there are API changes
Merging to get CI running again, we can walk back the API changes before releasing if needed. Thanks! |
We have this nice setting for having extension load failure raise errors instead of silently failing. We should respect it 😄