Update Beam Protobuf Schema (Java) - #35150
Conversation
9342333 to
23875da
Compare
|
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
6ae0d10 to
5e53125
Compare
|
I think that the many cases of |
|
I've removed I realized I had significantly misunderstood their proper usage. Nullability annotations on generics are only for specific use cases with strong reasoning (apparently a container-like class?). |
|
Run Java PreCommit |
1 similar comment
|
Run Java PreCommit |
|
Run Java_Amazon-Web-Services2_IO_Direct PreCommit |
|
@kennknowles could you review this pr again? Thanks |
|
Hi @kennknowles, can you review this PR when you get a chance? Thanks! |
|
Hello @kennknowles , are you able to review this PR when again? Thank you. |
kennknowles
left a comment
There was a problem hiding this comment.
I've got to admit it is hard for me to be certain I've checked enough to catch any potential problem. But I think I've done the best I can at this time. Hopefully we can get this tested via some real-world use cases and confirm it isn't breaking things in a way we can't recover from.
Honestly might want a second pair of eyes, like @reuvenlax
| return proto -> | ||
| ((List<Object>) proto) | ||
| .stream() | ||
| .map(element -> Preconditions.checkNotNull(elementConverter.convert(element))) |
There was a problem hiding this comment.
In general, the SDK's checkArgumentNotNull is preferred, because it throws IllegalArgumentException so that it clearly blames the caller, as it should in this case. Using Guava's checkNotNull causes it to the NPE which a user will correctly interpret as equivalent to a segfault in terms of the coding that led to it.
You don't have to fix it in this PR but it is a useful followup to just avoid Guava's checkNotNull entirely. I should make a checkstyle rule...
|
Confirmed that both test failures look like flakes. I'm re-running them. |
|
ready to merge @kennknowles ? |
|
Thanks for the fix ! Friendly ask : would you do a patch release of beam that includes this fix ? |
We usually do not do a patch release. If you need this now, you can use the SNAPSHOT version: https://github.com/apache/beam/blob/master/contributor-docs/code-change-guide.md#run-your-pipeline-with-modified-beam-code |
|
Probably caused https://github.com/apache/beam/actions/workflows/beam_PreCommit_Yaml_Xlang_Direct.yml?query=event%3Aschedule failing update: confirmed: https://github.com/apache/beam/actions/runs/18021430173 |
|
@Abacn it still failed after the revert: https://github.com/apache/beam/actions/runs/18023411365. I doubt if this change really caused the test failing. |
This reverts commit c3ef7f3.
|
@Abacn, thanks, a bug was found with I created #36297 to fix it, but I cannot run the test on the PR. Could you let me know how I can run the test? [1] |
Fix #35081.
Refer to https://s.apache.org/beam-protobuf.
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.