I might have missed this in the docs but is it expected that

Question

I might have missed this in the docs but is it expected that the flyte backend is backwards compatible with older `flytekit` versions We have some other dependencies blocking upgrading `flytekit` presently but would like to keep the backend services as up to date as possible

Yee · Answer

back to 1 0 of flytekit yeah

Rahul Mehta · Answer

Fantastic thanks for confirming < Yee>

Rahul Mehta · Answer

Hmm it unfortunately looks like there were some incompatibilities between the 1 3 0 chart amp flytekit 1 2 7 we were unable to run any dynamic steps that fanned out those tasks just stalled

Yee · Answer

those should definitely be compatible

Yee · Answer

why can t you upgrade flyte btw what are the dependency issues you re seeing

Rahul Mehta · Answer

We re unfortunately blocked on protobuf due to another dependency hilariously enough kubeflow pipelines

Yee · Answer

can you pull the futures file for the stalled tasks

Rahul Mehta · Answer

Ripping kubeflow out of our codebase soon but right now the dependency constraints on protobuf aren t compatble

Yee · Answer

so protobuf 3

Rahul Mehta · Answer

What s the futures file Happy to look for it

Yee · Answer

yeah

Yee · Answer

well maybe just look at the admin endpoint that might be easier

Rahul Mehta · Answer

Sorry could you clarify What should I be looking at

Yee · Answer

sorry afk

Rahul Mehta · Answer

So just saw some more interesting behavior we also hit this after rolling back but in this particular situation we had 3 concurrently running dynamic workflows that in turn all had gt 500 nodes in the pipeline it took approx an hour for the actual dynamic step to complete amp fan out but all of them are now executing