Changes to not catch exception related to coding errors#2522
Changes to not catch exception related to coding errors#2522joachimmetz wants to merge 1 commit into
Conversation
Onager
left a comment
There was a problem hiding this comment.
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