Open itzcoatl90 opened 3 years ago
java.lang.RuntimeException: only expecting one cleanup method per class
at com.uber.errorprone.checker.leaks.UnbalancedListener$CallScanner.visitMethod(UnbalancedListener.java:270)
This crash is likely a logic error in that check, which isn't one of the built-in ones.
Can you route this bug to whoever wrote the check you're using?
@itzcoatl90 If this UnbalancedListener
in Android monorepo at Uber, please reach out to me internally (lazaro@) or to the Programming Systems Group (there is a public support Slack channel). This is one of ours and we should take a look at it internally first 😄
@cushon I remember the answer being "no" years ago, but... is there a way to override the url/message shown on a checker crash to point people first to our internal channels? (Without forking) It would avoid this kind of mistaken report. Even when we run into issues with first-party Google checkers, it at least allows us to take a first look an upstream an issue with extra context.
I remember the answer being "no" years ago, but... is there a way to override the url/message shown on a checker
There still isn't configuration for that, but I'm not opposed to adding one.
Another option here is to just remove the crash report URL. We customize it to point to our internal issue tracker, for OSS maybe having com.google.errorprone
in the stack trace is good enough, especially since we end up catching crashes that don't original in core Error Prone (e.g. custom checks, or javac itself).
There still isn't configuration for that, but I'm not opposed to adding one.
We'd use it if it were available. If you want me to try to make a PR for it, let me know. I might not be able to get to it this week, but would definitely love having this as a configuration option.
Another option here is to just remove the crash report URL. We customize it to point to our internal issue tracker, for OSS maybe having
com.google.errorprone
in the stack trace is good enough, especially since we end up catching crashes that don't original in core Error Prone (e.g. custom checks, or javac itself)
You guys know better than I how Error Prone is mostly used. My assumption is that the long tail of "small" deployments benefit from the default crash report URL, and we would definitely love to have a custom message instead (over "no message" even, since even seeing com.uber.*
there won't exactly tell a new hire which team to contact 🙂 )
Description of the problem / feature request:
I was instructed to report this and post this information