Closed architrathore closed 2 weeks ago
Thank you for opening your first issue here! 🛠
The issue you're encountering is related to Flyte's handling of complex types, particularly nested dataclasses. According to this GitHub issue, nested dataclasses are not fully supported in Flyte's type system, which can lead to type mismatches during workflow compilation.
Would you like more detail on potential workarounds or further explanation of the issue?
Sources:
This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.
Mention @runllm to ask follow-up questions. See runllm.com for more!
Cc @ByronHsu
I think this is the bug of propeller, but not related to the JSON IDL. I'm investigating.
Describe the bug
As per Accessing Attributes documentation, accessing attributes on promises is supported in workflows. This works for simple types like str or int, but fails during workflow compilation for complex types such as accessing inner dataclass on a nested dataclasses.
Expected behavior
Accessing attributes should work for all types, not just primitive ones.
Additional context to reproduce
flytekit version==1.11.0
When registering the workflow, this fails with the following error:
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?