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
Workflow[...] failed. RuntimeExecutionError: max number of system retry attempts [51/50] exhausted. Last known status message:
Failed to check Catalog for previous results:
unexpected artifactData: [o0]
type: [union_type:<variants:<simple:STRING structure:<tag:"str" > > > ] does not match any task output
type: [union_type:<variants:<simple:STRING > variants:<simple:NONE > > ]
Error from flytepropeller log:
DataCatalog failed to get outputs from artifact dc8dc0fc-a61d-4126-85bd-34b163d49257,
err: unexpected artifactData: [o0]
type: [union_type:<variants:<simple:STRING structure:<tag:"str" > > > ] does not match any task output
type: [union_type:<variants:<simple:STRING > variants:<simple:NONE > > ]
Looking at underlying decoded proto, which is consistent with error message of deserialized type.
Cached task returning optional string (or other types) should be able to get output from the cache.
Optional type should be round-trip serializable. Specifically, it seems that the serialized proto data doesn't encode "optionality" of type here.
Additional context to reproduce
Task return_optional will fail after the first successful run caching its output
Thanks for confirming! Sorry we did look for issues related to this serialization but couldn't find, and assumed it wasn't due to version. We should do a better job here :) Definitely are prioritizing upgrading.
Describe the bug
Re-running a cached task returning
Optional[str]
would fail.For example:
Msg on Flyte console:
Error from flytepropeller log:
Looking at underlying decoded proto, which is consistent with error message of deserialized type.
Expected behavior
Cached task returning optional string (or other types) should be able to get output from the cache.
Optional type should be round-trip serializable. Specifically, it seems that the serialized proto data doesn't encode "optionality" of type here.
Additional context to reproduce
Task
return_optional
will fail after the first successful run caching its outputScreenshots
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: