[
https://issues.apache.org/jira/browse/HBASE-12187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113667#comment-17113667
]
Matthew Foley commented on HBASE-12187:
---------------------------------------
Not sure whether this ever got done or not, but seeing as the Jira is still
open, I thought y'all might be interested to know that a couple days ago,
[https://github.com/google/error-prone/pull/372] , consisting of these rules,
was finally merged into [error-prone|https://github.com/google/error-prone]!
No release yet, (last one was version 2.3.4 on 12/2/2019), but maybe someday :)
> 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)
