[
https://issues.apache.org/jira/browse/BEAM-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543807#comment-16543807
]
Thomas Weise commented on BEAM-4784:
------------------------------------
Interesting. I had run clean before, but only for the container and not taking
into account the sdist dependencies.
Now the sdist build succeeds and shows
{code:java}
Collecting protobuf>=3.2.0 (from grpcio-tools==1.3.5){code}
instead of
{code:java}
Collecting protobuf>=3.5.0.post1 (from grpcio-tools<2,>=1.3.5){code}
Does this mean the grpcio-tools dependency changed in a way that does not cause
an update?
The good news is that my example pipeline again works with the latest master.
Thanks!
> Python SDK harness container build fails
> ----------------------------------------
>
> Key: BEAM-4784
> URL: https://issues.apache.org/jira/browse/BEAM-4784
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Reporter: Thomas Weise
> Assignee: Robert Bradshaw
> Priority: Major
> Fix For: 2.6.0
>
>
> A new build failure has surfaced for ./gradlew -p sdks/python/container
> docker (fails in :beam-sdks-python:sdist)
> It can be reproduced even on a commit that succeeded before. Basically it
> attempts to retrieve protobuf for several minutes before it finally fails
> with "RuntimeError: maximum recursion depth exceeded"
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
