-
Notifications
You must be signed in to change notification settings - Fork 1.2k
KotlinWhenStringFilter: remove filtering for Scala classes #1224
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
KotlinWhenStringFilter: remove filtering for Scala classes #1224
Conversation
This removes a Jacoco bug for some Scala 2.13 classes.
d44bd7d
to
44d3c98
Compare
@gergelyfabian Can you please provide an example class file which causes the NPE described in bazel-contrib/rules_scala#1291? JaCoCo should never throw a NPE when processing valid class files. We should therefore fix the root cause and not just check the case when the class was compiled from Scala. |
@marchof Of course. Sorry I guess maybe I should have first opened an issue for this. Here is a class that reproduces it (if compiled with Scala 2.13): Should I provide it as a .class file? |
Yes, please. Thx! |
Sure, so how I generated the class file:
What would be the preferred way to provide you the file? |
Just attach the jar here. |
I renamed the jar to zip, to be able to attach it. |
Stacktrace
indicates that there should be call of Iterating by our tags from most recent And between
there was fix #942 in version Also using JaCoCo Command Line Interface version
whereas version
So @gergelyfabian are you sure that you're using latest released JaCoCo version ( |
In addition to inability to reproduce with version
|
Thanks @Godin! I'm using Jacoco 0.8.3 that's used by the current Bazel release (4.1.0). To be more exact, more frequently I use a custom version of Jacoco, that contains some fixes on top of 0.8.3 (that's the only compatible version with last released Bazel). So if this is a duplicate of #942, then I'll try to backport the fix for #942 on the custom branch of Jacoco that I use, and I should be done (and be safe that a later upgrade of Jacoco in Bazel will remove the need for my custom branch of Jacoco). |
I can just confirm, that backporting the fix for #942 fixes this issue. |
This removes a Jacoco bug for some Scala 2.13 classes.
Bug report in bazel-contrib/rules_scala#1291.