-
Notifications
You must be signed in to change notification settings - Fork 351
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
Changes to not catch exception related to coding errors #2522
base: main
Are you sure you want to change the base?
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.
Can you explain the rationale for this? Why would we want to crash at runtime if there's a bug?
Pylint and unittests can catch these exceptions when not absorbed by the try except let's chat about this, I've noticed a couple of time (not specific to plaso) that the broad try except absorbs some exception that could have been caught by the tests. Which then later on lead to other subtle issues. |
I can see this happening in tests, but I don't understand could catch any more problems with a specific try-catch block. Can you give an example? |
e84237d
to
2425e32
Compare
Codecov Report
@@ Coverage Diff @@
## main #2522 +/- ##
==========================================
- Coverage 85.68% 85.60% -0.08%
==========================================
Files 379 379
Lines 32389 32421 +32
==========================================
+ Hits 27751 27755 +4
- Misses 4638 4666 +28
Continue to review full report at Codecov.
|
@Onager PTAL |
Changes to not catch exception related to coding errors