tvalentyn opened a new pull request, #37817:
URL: https://github.com/apache/beam/pull/37817

   Context: We discovered that Go precommit suite was failing (#32324) after 
GRPC 1.66 update  (https://github.com/grpc/grpc/issues/37710). 
   
   GRPC team believes that this error is triggered by a somewhat specific usage 
scenario in the Go postcommit suite, caused by the suite running multiple go 
tests in parallel and there is not sufficient reason to believe that Beam users 
would also be affected (cc: @sergiitk to keep me honest). 
   
   On the other hand, Beam users are adversely affected by a capped lower bound 
on grpcio. We still anticipate a proper fix in 
https://github.com/grpc/grpc/issues/37710, and it might arrive in 
grpcio==1.72.2. However, given that grpcio==1.72.1 was yanked, we are 
proceeding with removing the grpc lower bound to ensure that Beam users have a 
compatible grpc requirement in Beam 2.72.0. Out of caution, we are not planning 
to update GRPCIO in the default beam SDK containers in 2.72.0, keeping them on 
1.65.x. Beam users would be able to install newer versions of GRPCIO though. 
   
   Some confidence in this approach is that Beam Python 3.13 users have been on 
newer versions on GRPC and we are not aware of issues.
   
   GRPC version 1.70.x and earlier are affected by a known issue 
https://github.com/grpc/grpc/issues/38290#issuecomment-3014966368 , hence 
keeping those out of the allowed range.
   
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] Mention the appropriate issue in your description (for example: 
`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, comment `fixes #<ISSUE NUMBER>` instead.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/actions/workflows/build_wheels.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/actions/workflows/python_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/actions/workflows/java_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/actions/workflows/go_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI or the [workflows 
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) 
to see a list of phrases to trigger workflows.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to