Conversation
|
Assigning reviewers. If you would like to opt out of this review, comment R: @jrmccluskey for label python. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
tvalentyn
left a comment
There was a problem hiding this comment.
PTAL at test/lint errors.
Co-authored-by: tvalentyn <tvalentyn@users.noreply.github.com>
|
.github/workflows/beam_PreCommit_Python_Coverage.yml https://github.com/apache/beam/actions/runs/13738774760/job/38433034429?pr=34196 [gw5] [ 97%] FAILED apache_beam/runners/portability/portable_runner_test.py::PortableRunnerTestWithSubprocesses::test_combine_per_key |
|
https://github.com/apache/beam/actions/runs/13738774755/job/38433041471?pr=34196 |
|
Also launched GoPortable presubmit suite on these changes: https://github.com/apache/beam/actions/runs/13814130500 That is the suite that was previously failing on new versions of grpc. |
|
|
|
https://github.com/apache/beam/actions/runs/13814130500/job/38824779287 also keeps failing. |
|
1.71: still timeout for many tests. |
|
Reminder, please take a look at this pr: @jrmccluskey |
|
Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment R: @damccorm for label python. Available commands:
|
|
Mark this as a blocker for Beam 2.65.0. |
|
Reminder, please take a look at this pr: @damccorm |
|
blocked by grpc/grpc#39113 |
|
stop reviewer notifications |
|
Stopping reviewer notifications for this pull request: requested by reviewer. If you'd like to restart, comment |
|
note: there may be additional, yet to be studied issue in grpc 1.66.0., the original reason why the upper bound was introduced. |
|
is this still targeted to 2.65.0 ? cc: @liferoad @tvalentyn |
|
grpc/grpc#39894 is out to fix this with 1.73.1 |
| 'grpcio>=1.67.0; python_version >= "3.13"', | ||
| # any version between 1.68.0 and 1.73.0 is bad | ||
| # external issue: https://github.com/grpc/grpc/issues/37710 | ||
| 'grpcio>=1.33.1,<1.74.0,!=1.48.0,!=1.59.*,!=1.60.*,!=1.61.*,!=1.62.0,!=1.62.1,!=1.68.*,!=1.69.*,!=1.70.*,!=1.71.*,!=1.72.*,!=1.73.0; python_version <= "3.12"', # pylint: disable=line-too-long |
There was a problem hiding this comment.
Do we still need the <1.74.0 condition? Theoretically grpcio should have forward compatibility, and blocking this could lead to dependency conflicts. It would also be nice to allow the same versions which we allow for 3.13.
I'd also be fine waiting a few releases to see if grpcio remains stable for us though
There was a problem hiding this comment.
We probably do no need <1.74.0 but given the wide range has caused a lot of issues for us, I would suggest we use the tighter bound with Python <= 3.12.
There was a problem hiding this comment.
Ok - I'm fine with this for now, eventually I'd like to get rid of it once we've built some confidence in this again
There was a problem hiding this comment.
I would use the same upper bound for all python versions. I think it should be fine to keep the first line and remove the python_version modifier.
There was a problem hiding this comment.
Also, we should check if Go tests still break with this.
There was a problem hiding this comment.
Also, we should check if Go tests still break with this.
Launched https://github.com/apache/beam/actions/runs/15907748034
|
Thanks for following up on this |
|
I am going to merge this now so we have more time to test the potential impact from this. |
* Removed < 1.66 for grpcio * Update sdks/python/setup.py Co-authored-by: tvalentyn <tvalentyn@users.noreply.github.com> * updated the version upper bound * skip pip check for lint * try <1.71 * updated the grpcio range * use grpcio 1.73.1 --------- Co-authored-by: tvalentyn <tvalentyn@users.noreply.github.com>

We can merge this after the Beam 2.64.0 release cut on March 19 to check whether grpcio still causes issues.
Fixes #34081
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.