This message was deleted.

@Bo Yes, you can try updating the

protobuf

version in

flytekit

to be compatible with both

mlflow

and

bentoml

. You can also try downgrading the

protobuf

version in

mlflow

to be compatible with

flytekit

. Another option is to use a virtual environment to isolate the dependencies for each project.

This doesn’t look like a solution - I can’t downgrade protobuf version in external libraries

We only provide a upperbound

protobuf<4.0

but not sure how it got locked

I have the same issue. Is there plans for BentoML to support protobuf >= 4?

@Aaron Pham So do you think it’s a bug or am I doing something wrong here? I’m simply adding bentoml (along with flytekit) to my requirements.in and running pip-compile and it’s throwing this error.

can you try to put

protobuf>3,<5

? I believe this is a transitive dependencies from opentelemetry

You mean explicitly add protobuf as a dependency?

yes, to your requirements.txt for now.

Still no good I think: added to requirements.in:

There are incompatible versions in the resolved dependencies:
  protobuf<5,>3 (from -r /xxx (line 6))
  protobuf>=3.0.0 (from protoc-gen-swagger==0.1.0->flyteidl==1.3.17->flytekit==1.5.0->-r /xxx (line 7))
  protobuf!=3.20.0,!=3.20.1,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5 (from googleapis-common-protos==1.59.0->flytekit==1.5.0->-r /xxx (line 7))
  protobuf~=3.13 (from opentelemetry-proto==1.14.0->opentelemetry-exporter-otlp-proto-http==1.14.0->bentoml==1.0.15->-r /xxx (line 4))
  protobuf<5.0.0,>=4.21.1 (from flyteidl==1.3.17->flytekit==1.5.0->-r /xxx (line 7))
  protobuf>=4.21.6 (from grpcio-status==1.53.0->flytekit==1.5.0->-r /xxx (line 7))