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
False positive for DirectInvocationOnMock #3396
Comments
trask
added a commit
to open-telemetry/opentelemetry-java-instrumentation
that referenced
this issue
Sep 23, 2022
(note that change from BDDMockito is due to google/error-prone#3396)
LironKS
pushed a commit
to helios/opentelemetry-java-instrumentation
that referenced
this issue
Oct 23, 2022
(note that change from BDDMockito is due to google/error-prone#3396)
LironKS
pushed a commit
to helios/opentelemetry-java-instrumentation
that referenced
this issue
Oct 31, 2022
(note that change from BDDMockito is due to google/error-prone#3396)
LironKS
pushed a commit
to helios/opentelemetry-java-instrumentation
that referenced
this issue
Dec 4, 2022
(note that change from BDDMockito is due to google/error-prone#3396)
Thanks for creating this issue. I was going to make one. Is this still under consideration? |
#3731 will address this issue |
Still looking to get this reviewed & approved - everything should be ready, except the build does not pass as I've not been approved by a maintainer to run workflows. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code like this should be allowed for
DirectInvocationOnMock
:The text was updated successfully, but these errors were encountered: