Description of the problem / feature request:
Trying out bazel 4.0.0, with --javabase=@bazel_tools//tools/jdk:remote_jdk11 --java_toolchain=@bazel_tools//tools/jdk:toolchain_java11 and hit a bug in error-prone 2.4.0 (bazel 3.3.1 has 2.3.2 I think, and it works)
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Haven't yet reproduced in a small setup but likely is triggered by code generated by https://github.com/immutables/immutables 2.8.8
Any other information, logs, or outputs that you want to share?
Most recent error_prone is 2.5.1, but haven't tested if it'd fix the issue https://github.com/google/error-prone/releases
some_class.java:192: error: An unhandled exception was thrown by the Error Prone static analysis plugin.
SomeClass.builder().from(someInstance).build())
Please report this at https://github.com/google/error-prone/issues/new and include the following:
error-prone version: 2.4.0
BugPattern: ArrayToString
Stack Trace:
java.lang.StackOverflowError
at jdk.compiler/com.sun.tools.javac.code.Types$UnaryVisitor.visit(Types.java:4937)
at jdk.compiler/com.sun.tools.javac.code.Types.supertype(Types.java:2462)
at jdk.compiler/com.sun.tools.javac.code.Types$12.visitClassType(Types.java:2128)
at jdk.compiler/com.sun.tools.javac.code.Types$12.visitClassType(Types.java:2117)
at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.accept(Type.java:993)
at jdk.compiler/com.sun.tools.javac.code.Types$DefaultTypeVisitor.visit(Types.java:4857)
at jdk.compiler/com.sun.tools.javac.code.Types.asSuper(Types.java:2114)
at jdk.compiler/com.sun.tools.javac.code.Types$12.visitClassType(Types.java:2130)
at jdk.compiler/com.sun.tools.javac.code.Types$12.visitClassType(Types.java:2117)
at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.accept(Type.java:993)
at jdk.compiler/com.sun.tools.javac.code.Types$DefaultTypeVisitor.visit(Types.java:4857)
at jdk.compiler/com.sun.tools.javac.code.Types.asSuper(Types.java:2114)
at jdk.compiler/com.sun.tools.javac.code.Types$12.visitClassType(Types.java:2130)
at jdk.compiler/com.sun.tools.javac.code.Types$12.visitClassType(Types.java:2117)
at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.accept(Type.java:993)
at jdk.compiler/com.sun.tools.javac.code.Types$DefaultTypeVisitor.visit(Types.java:4857)
...
Not sure if there's an easy way to upgrade error_prone version without the need to rebuild bazel itself
Bump of error_prone commit 239b2aa
Some issues with earlies attempts of upgrade 2.3.2->2.3.3 #9286
Description of the problem / feature request:
Trying out bazel 4.0.0, with
--javabase=@bazel_tools//tools/jdk:remote_jdk11 --java_toolchain=@bazel_tools//tools/jdk:toolchain_java11and hit a bug in error-prone 2.4.0 (bazel 3.3.1 has 2.3.2 I think, and it works)Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Haven't yet reproduced in a small setup but likely is triggered by code generated by https://github.com/immutables/immutables 2.8.8
Any other information, logs, or outputs that you want to share?
Most recent error_prone is 2.5.1, but haven't tested if it'd fix the issue https://github.com/google/error-prone/releases
Not sure if there's an easy way to upgrade error_prone version without the need to rebuild bazel itself
Bump of error_prone commit 239b2aa
Some issues with earlies attempts of upgrade 2.3.2->2.3.3 #9286