anyone know why pyflinks protobuf version is pinne...
# random
f
anyone know why pyflinks protobuf version is pinned at
<3.18
for 1.15?
m
Most likely because there was another dependency that required a lower version of it
f
ah interesting yeah that would make sense since i think older versions allowed versions above this so it must be a transitive dep
m
Most likely yes, especially since Protobuf is used by so many things πŸ˜…
πŸ˜… 1
And we usually don't do dependency upgrades in patch versions
f
Ah looks like this dependency might be the one grpcio
t
Yeah, I've been dealing with this in StateFun and Java for about a week now.
StateFun
is pinned at
3.7.1
which has been an absolute nightmare. I had to compile my Protos with the
3.7.1
protoc(much lower than
3.21.10
I was using). That got my Elasticsearch IO Module running.
But then I have a Remote Functions App in Java that I cannot get running due to
FunctionTo
not being present for some reason(another version conflict). So far I've not heard any kind of answer as to this fiasco and it seems to extend through the Flink ecosystem.