-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Illegal reflective access by com.google.protobuf.UnsafeUtil when running Bazel 0.17.1 #6151
Comments
We should suppress those warnings, but it's harmless to ignore them for now. And you should only see these on startup, i.e. subsequent runs of |
I see them during every build, not just on startup. INFO: From Checking the completeness of the deps for external/androidx_vectordrawable_vectordrawable_1_0_0_beta01/_aar/androidx_vectordrawable_vectordrawable_1_0_0_beta01/classes_and_libs_merged.jar:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/private/var/tmp/_bazel_jgavris/install/5d78d317e261432eb3abd12e67760ca9/_embedded_binaries/embedded_tools/src/java_tools/import_deps_checker/java/com/google/devtools/build/importdeps/ImportDepsChecker_deploy.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release |
That's a different instance of the same problem, the same suppression flags are needed here too: bazel/src/java_tools/import_deps_checker/java/com/google/devtools/build/importdeps/BUILD.tools Line 11 in 1f684e1
|
When buliding an android app it does spit out a lot of them building the build, it seems everytime a java process it started. |
See #6151 See also #5978 (comment). PiperOrigin-RevId: 213216870
Was this fixed? |
Several of us on Angular team observed this after update to 0.18 |
Building Bazel HEAD using Bazel 0.18.0 in IntelliJ on my Arch Linux box (no matter if system JDK is 8 or 10) spams the build log with ~100 of these annoying messages. |
@alexeagle @philwo this affects every Java binary that transitively depends on protos: protocolbuffers/protobuf#3781 Which specific tools are you seeing generate warnings? The fix is to add the following JVM flags:
|
@cushon This is what I'm seeing:
I guess it comes from our IntelliJ plugin? |
See bazelbuild/bazel#6151 (comment) for an explanation. cc @cushon
I'm getting it, and I quote: "From parsing Android resources for //path/to/package". Then I get the full set of warnings. It'd be superlatively nice to shut them up, especially since literally every android_library seems to be triggering it. I really don't want to add it to every library target. |
Still happens with
|
Dupe of #5439? |
This is fixed as of Bazel from today. |
Description of the problem / feature request:
I install Bazel 0.17.1 in a fresh ubuntu:xenial container using the installer.sh, and when I run bazel version it gives the following warnings:
bazel version
Extracting Bazel installation...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/root/.cache/bazel/_bazel_root/install/28c1d2ace0add449e21862ae9f2d2289/_embedded_binaries/A-server.jar) to field java.lang.String.value
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
Build label: 0.17.1
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri Sep 14 10:39:25 2018 (1536921565)
Build timestamp: 1536921565
Build timestamp as int: 1536921565
Feature requests: what underlying problem are you trying to solve with this feature?
I'm just not sure if that's expected with the new version.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
ubuntu xenial docker container
What's the output of
bazel info release
?bazel info release
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/root/.cache/bazel/_bazel_root/install/28c1d2ace0add449e21862ae9f2d2289/_embedded_binaries/A-server.jar) to field java.lang.String.value
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
ERROR: The 'info' command is only supported from within a workspace.
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
Have you found anything relevant by searching the web?
#5599
The text was updated successfully, but these errors were encountered: