You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to so all the setup necessary to work on some features for flytekit but I'm getting hung up on running make dev-requirements.txt I was able to do the initial setup described in the Contributing guide, but as I understand it, for extras and plugins, we should add these optional requirements to dev-requirements.in. Here's the error I'm getting:
I'm using a conda environment instead of using the recommended virtualenv, but this should work, and it did for the initial setup. I have tried this in a fresh environment using
conda create -n flyte-dev python=3.8
conda activate flyte-dev
make dev-requirements.txt
But still get this error.
From a discussion on Slack, it was suggested that this is due to a new version of grpcio (1.50.0) is pulling in a version of protobuf >= 4. The suggested fix is to include grpcio<=1.47.0 and grpcio-status<=1.47.0 to requirements.in.
I'll try this in a PR.
Expected behavior
Running make dev-requirements.txt should run without failure.
Additional context to reproduce
conda create -n flyte-dev python=3.8
conda activate flyte-dev
make dev-requirements.txt
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm trying to so all the setup necessary to work on some features for flytekit but I'm getting hung up on running
make dev-requirements.txt
I was able to do the initial setup described in the Contributing guide, but as I understand it, for extras and plugins, we should add these optional requirements todev-requirements.in
. Here's the error I'm getting:I'm using a conda environment instead of using the recommended virtualenv, but this should work, and it did for the initial setup. I have tried this in a fresh environment using
But still get this error.
From a discussion on Slack, it was suggested that this is due to a new version of grpcio (1.50.0) is pulling in a version of protobuf >= 4. The suggested fix is to include
grpcio<=1.47.0
andgrpcio-status<=1.47
.0 torequirements.in
.I'll try this in a PR.
Expected behavior
Running
make dev-requirements.txt
should run without failure.Additional context to reproduce
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: