-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug]: Bytebuddy version update causes Invisible parameter type error #22749
Comments
Unvendored and updated bytebuddy version in PR #17317 |
Out of curiosity does the test pass if we are using bytebuddy 1.11.0 implying a backwards incompatible change with bytebuddy and not due to the unshading of bytebuddy? |
I'm seeing it pass with bytebuddy 1.12.3 and earlier, and fail with bytebuddy 1.12.4 and later, regardless of unshading: raphw/byte-buddy#1301 So this is concerning, but it seems like it would have been an issue regardless of unshading when the dependency was upgraded. |
Thanks, linking the release thread where this was initially communicated for context around the issue: https://lists.apache.org/thread/zxtj1pr81l5nqqxsc4mjwnssflg8jkth |
To work around apache#22749
I may confirm that I have the same results with different bytebuddy version on my side as @cushon provided above. Does anyone have an idea why it doesn't fail with Beam CI jobs/tests? |
The bytebuddy regression involves handling of classes in the default package, and the failure from Talend/beam-samples involves a class in the default package: https://github.com/Talend/beam-samples/blob/74b5dfae2b2d1ac4e1272467e7d4584f852b0888/serializableTests/src/test/java/SerializationTest.java#L22. Is it possible the Beam CI isn't exercising transformation of classes in the default package? |
Right, I don't think we have Java files with default package:
(this found one should be fixed) |
Removing the milestone since it's rolled back for the release |
This release includes the fix for the issue with visibility checks for types in the default package that caused apache#22749.
This release includes the fix for the issue with visibility checks for types in the default package that caused apache#22749.
To work around apache#22749
@aromanenko-dev @cushon is this now resolved? We first reverted for the release, then downgraded the unvendored bytebuddy on the master branch. Do we have confirmation that it is fixed? |
It's fixed now: #22814 upgraded to the latest bytebuddy version, which includes a fix, and added a local regression test. |
To work around apache#22749
This release includes the fix for the issue with visibility checks for types in the default package that caused apache#22749.
To work around apache#22749
This release includes the fix for the issue with visibility checks for types in the default package that caused apache#22749.
To work around apache#22749
This release includes the fix for the issue with visibility checks for types in the default package that caused apache#22749.
What happened?
org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Invisible parameter type of SerializationTest$1 arg0 for public SerializationTest$1$DoFnInvoker(SerializationTest$1)
https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true
Issue Priority
Priority: 1
Issue Component
Component: dependencies
The text was updated successfully, but these errors were encountered: