Hi team.. Gotten stuck with a dataclass (which is an output of a different task) that perpetually co...
l
Hi team.. Gotten stuck with a dataclass (which is an output of a different task) that perpetually converts an int into a float, resulting in the pipeline breaking further along. It used to be a NamedTuple, which I had to convert into dataclass due to a different pipeline not “liking” NamedTuple. For the dataclass itself, I even tried to define from_dict and to_dict functions to force the correct data types, but no luck I’m using flytekit 13.3.3
I saw some threads with similar issues, but didn’t find a clear solution
d
Can you try flytekit 1.14.0?
This will solve the problem
f
Upgrade please
l
I tried.. and a different pipeline broke in the registering phase and I was in a rush to fix.. so for now I defined everything as floats and am casting at the point of use. I’ll give the upgrade a try next
1 odd thing I did notice though is that even though my backend is 1.13 and I briefly tried flytekit 1.14, and as per docs it should be using the old serialization format, I did see this in the output of the task
d
you have to update your flyteconsole
l
once it’s updated across the board would the outputs show up like runs prior to 1.14? I.e. actual values?
c
yes, @little-cricket-84530. That's the expectation. You should update flyteconsole to at least https://github.com/flyteorg/flyteconsole/releases/tag/v1.19.0.