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
There are cases where, when passing dataclass promises around between workflows and tasks, they fail to deserialize properly. This appears to be related to a bug in the protobuf Message parsing, namely that _MessageToDictdoesn't always return a dict when deserializing, it can return a list if that's what the input should deserialize to.
Expected behavior
It should be possible to use dataclasses that contain lists without issue.
This issue appears to be related to the known problem with Flyte's handling of dataclasses containing lists, particularly during serialization and deserialization. The root cause is that _MessageToDict can return a list instead of a dict, which Flyte's type system does not handle correctly.
According to this GitHub issue, the problem arises because _MessageToDict does not always return a dict when deserializing, leading to errors when Flyte tries to process the data. This issue has been acknowledged and is being tracked.
Would you like more detail on potential workarounds or further explanation of the issue?
Describe the bug
There are cases where, when passing dataclass promises around between workflows and tasks, they fail to deserialize properly. This appears to be related to a bug in the protobuf Message parsing, namely that
_MessageToDict
doesn't always return a dict when deserializing, it can return a list if that's what the input should deserialize to.Expected behavior
It should be possible to use dataclasses that contain lists without issue.
Additional context to reproduce
The above throws an exception around trying to access a list like a dict.
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: