DerRidda commented on issue #30867: URL: https://github.com/apache/beam/issues/30867#issuecomment-2040607446
> Thanks. > > ``` > (py38) :python$ docker run --rm -it --entrypoint=/bin/sh apache/beam_python3.10_sdk:2.53.0 -c "pip list | grep grpcio" > grpcio 1.59.3 > grpcio-status 1.59.3 > (py38) :python$ docker run --rm -it --entrypoint=/bin/sh apache/beam_python3.10_sdk:2.54.0 -c "pip list | grep grpcio" > grpcio 1.60.0 > grpcio-status 1.60.0 > (py38) :python$ docker run --rm -it --entrypoint=/bin/sh apache/beam_python3.10_sdk:2.55.0 -c "pip list | grep grpcio" > grpcio 1.62.0 > grpcio-status 1.62.0 > (py38) :python$ docker run --rm -it --entrypoint=/bin/sh apache/beam_python3.10_sdk:2.55.1 -c "pip list | grep grpcio" > grpcio 1.62.0 > grpcio-status 1.62.0 > ``` > > > I could determine that at least version 1.60.0 doesn't exhibit this issue. > > Double checking, is this still the case? Actually still happens on 1.60.0 for me. It just looked fixed for a brief moment. The known good version of my pipeline probably uses 1.59.3 as I changed the SDK container image to be fully custom as well in the update so even though the project local deps were showing 1.60.0 it never got installed into the image of the known good service. I will investigate more on Monday. -- 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: github-unsubscr...@beam.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
