This message was deleted.

I don't believe BentoML should be locking the protobuf version? I think we really need to migrate some of the server stuff somehow; the opentelemetry dependencies are pretty annoying. @Aaron Pham what was the conclusion of the otel dependency discussion?

We shouldn’t lock the protobuf version. The reason I put a soft upper bound is that protobuf 4 won’t work with tensorflow, onnx and many others ml frameworks. wrt the otel dependency, we need to have a monitoring tests in bentoml to make sure that it works when we upgrade otel. Since we don’t have a test for it right now, idk if we can just freely update otel

I don't think we should lock otel dependencies at all, right?

we need to lock it to make it work

Thanks for the replies guys. I was wondering if there is any way to exclude

opentelemetry

from

bentoml

for my project to work with the latest versions of both

bentoml

and

flytekit

You can just install flytekit, pip might complain but it should work ok.

I’m having this problem as well - I use

pip-compile

and I don’t think it lets us ignore the conflicts. Is there an ETA on bumping up the protobuf version to 4?

Is the

protobuf<4

coming from

opentelemetry

?

It seems so - in my case it seems to lock it to ~=3.13 due to

opentelemetry

but that’s probably because I’m using pip-compile

Yeah, I'm not sure what the correct way to do this is... We've locked otel because they keep making breaking changes, which means our server APIs wouldn't work if we didn't. @Jiang maybe we can make more of the otel dependencies optional?

@sauyon It'd be very convenient for me if otel dependencies were optional. If you plan to make this change, would it be anytime soon?

We'd probably try to get it out in the next release or so, maybe next week or the week after.

OK that’s good to know - I can work with it if I can remove the otel dependency. Thanks!

@sauyon amazing! thanks