https://flyte.org logo
#ask-the-community
Title
# ask-the-community
r

Rahul Mehta

04/10/2023, 9:59 PM
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
y

Yee

04/10/2023, 10:18 PM
back to 1.0 of flytekit yeah
r

Rahul Mehta

04/10/2023, 10:26 PM
Fantastic, thanks for confirming @Yee
Hmm, it unfortunately looks like there were some incompatibilities between the 1.3.0 chart & flytekit 1.2.7 (we were unable to run any dynamic steps that fanned out/those tasks just stalled)
y

Yee

04/12/2023, 4:31 PM
those should definitely be compatible.
why can’t you upgrade flyte btw? what are the dependency issues you’re seeing?
r

Rahul Mehta

04/12/2023, 4:32 PM
We're unfortunately blocked on protobuf due to another dependency (hilariously enough, kubeflow pipelines)
y

Yee

04/12/2023, 4:32 PM
can you pull the futures file for the stalled tasks?
r

Rahul Mehta

04/12/2023, 4:32 PM
Ripping kubeflow out of our codebase soon, but right now the dependency constraints on protobuf aren't compatble
y

Yee

04/12/2023, 4:33 PM
so protobuf 3
r

Rahul Mehta

04/12/2023, 4:33 PM
What's the futures file? Happy to look for it
y

Yee

04/12/2023, 4:33 PM
yeah
well maybe just look at the admin endpoint, that might be easier.
r

Rahul Mehta

04/12/2023, 4:44 PM
Sorry, could you clarify? What should I be looking at?
y

Yee

04/12/2023, 5:02 PM
sorry afk
r

Rahul Mehta

04/14/2023, 12:37 AM
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 >500 nodes in the pipeline). it took approx. an hour for the actual dynamic step to complete & fan-out, but all of them are now executing
79 Views