[
https://issues.apache.org/jira/browse/HBASE-12187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129775#comment-17129775
]
Ding Yuan commented on HBASE-12187:
-----------------------------------
[~mattf] the empty catch block rule is now part of [error-prone's newest
release (v2.4.0)|https://github.com/google/error-prone/releases/tag/v2.4.0].
This is by far the most important rule among Aspirator's rules (vast majority
of the bugs fall under this category). Try it :)
> Review in source the paper "Simple Testing Can Prevent Most Critical Failures"
> ------------------------------------------------------------------------------
>
> Key: HBASE-12187
> URL: https://issues.apache.org/jira/browse/HBASE-12187
> Project: HBase
> Issue Type: Bug
> Reporter: Michael Stack
> Priority: Critical
> Attachments: HBASE-12187.patch, abortInOvercatch.warnings.txt,
> emptyCatch.warnings.txt, todoInCatch.warnings.txt
>
>
> Review the helpful paper
> https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf
> It describes 'catastrophic failures', especially issues where exceptions are
> thrown but not properly handled. Their static analysis tool Aspirator turns
> up a bunch of the obvious offenders (Lets add to test-patch.sh alongside
> findbugs?). This issue is about going through code base making sub-issues to
> root out these and others (Don't we have the test described in figure #6
> already? I thought we did? If we don't, need to add).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
