Fix an invalid signature in ByteBuddyDoFnInvokerFactory #33984
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This code is creating a field with the same type as a method return type. The return type is erased, but calling `getGenericSignature()` turns the erased type back into a generic type. For methods with type parameters, this results in signatures that are invalid for field declarations, for example `<T:Ljava/lang/Object;>Ljava/lang/Object;Ljava/io/Serializable;`. Future versions of bytebuddy reject the invalid signature. See also raphw/byte-buddy#1771
Abacn
approved these changes
Feb 13, 2025
|
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
|
test failures unrelated, merging for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This code is creating a field with the same type as a method return type. The return type is erased, but calling
getGenericSignature()turns the erased type back into a generic type. For methods with type parameters, this results in signatures that are invalid for field declarations, for example<T:Ljava/lang/Object;>Ljava/lang/Object;Ljava/io/Serializable;. Future versions of bytebuddy reject the invalid signature.See also raphw/byte-buddy#1771
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.