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
setup.py has protobuf<5,>3, so I would expect version of protobuf in that range to work. More concretely, tensorflow tensorflow/tensorflow@60d5bfb requires protobuf >= 3.9.2, < 3.20' and it is reasonable to want to use tensorflow and feast together.
I first noticed this with the 0.26.0 release, but 0.25.1 is when I can first reproduce the problem.
Code generated with version X is only guaranteed to work with clients X>=1. So the minimal version of protobuf supported by feast becomes whatever version was used in in CI to generate, not the version in setup.py. I think the solution would look something like "compile-protos-python uses a separate environment with a fixed version of protobuf". I'm not sure if Makefile changes or github action configs would be the more palatable approach to doing that.
Expected Behavior
setup.py
hasprotobuf<5,>3
, so I would expect version of protobuf in that range to work. More concretely, tensorflow tensorflow/tensorflow@60d5bfb requiresprotobuf >= 3.9.2, < 3.20'
and it is reasonable to want to use tensorflow and feast together.I first noticed this with the 0.26.0 release, but 0.25.1 is when I can first reproduce the problem.
Current Behavior
feast 0.25.0
feast 0.25.1
Specifications
Feast SDK Version: "feast 0.25.1"
Linux 5.4.x
x86_64
Some history in #3103
The text was updated successfully, but these errors were encountered: