-
Notifications
You must be signed in to change notification settings - Fork 156
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
Update protobuf-java to 3.25.6 #1748
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Error: [01/26/2025 00:23:59.363] [RemoteRouterSpec-pekko.remote.default-remote-dispatcher-7] [Deserializer(pekko://RemoteRouterSpec)] Failed to deserialize message from [unknown] with serializer id [17] and manifest [d].
java.lang.UnsupportedOperationException: As of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2
at org.apache.pekko.protobufv3.internal.GeneratedMessage.warnPre22Gencode(GeneratedMessage.java:327)
at org.apache.pekko.protobufv3.internal.GeneratedMessageV3.makeExtensionsImmutable(GeneratedMessageV3.java:531)
I'm confused by this error, suggesting this should not happen as of version 21.7 but then recommending to regenerate with 25.6 or later. I can regenerate the classes though. |
@raboof thanks for rebuilding the Java files. They are not regenerated by the Pekko build. It looks like protobuf-java 3.25.6 has a new check so that it insists that you have generated the source with a more up to date version of Protoc that we have used for recent upgrades. It does look like something we would want to fix up for the 1.2.0-M1 release. If this PR builds ok, it is enough - I'm not worried about automating the code generation. I was trying this myself but my Mac won't let me use the protoc file from Google's releases on GitHub. I was in the middle of building it myself. |
e3fa87a
to
77f69ea
Compare
yeah, it's confusing to me that the error is referring to 21.7 but seems to trigger for all versions before 25.6, though.
agreed
ah, I used the 'assign' feature in GitHub to signal that I was looking into it (it didn't seem worth a comment) |
Looks like we have some more old java files in our tests (distributed data). Affects 2 tests. In the 'docs' module as opposed to the code modules. TwoPhaseSetMessages
|
c6b2c87
to
77f69ea
Compare
77f69ea
to
91c83dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
About this PR
π¦ Updates com.google.protobuf:protobuf-java from
3.25.5
to3.25.6
π GitHub Release Notes - Version Diff
Usage
β Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a
.scala-steward.conf
file.Have a fantastic day writing Scala!
π Files still referring to the old version number
The following files still refer to the old version number (3.25.5).
You might want to review and update them manually.
β Adjust future updates
Add this to your
.scala-steward.conf
file to ignore future updates of this dependency:Or, add this to slow down future updates of this dependency: