Closed RRap0so closed 3 months ago
The error you're encountering seems to be related to Flytekit's handling of output types when triggering a remote LaunchPlan. Specifically, the issue arises when Flytekit attempts to process a FlyteLiteral
that lacks the metadata
field, leading to a TypeError: 'NoneType' object is not subscriptable
.
This issue is not explicitly mentioned in the provided data sources. However, similar issues with Flytekit's handling of remote executions and type conversions have been reported. For example, issues related to NoneType
errors and type handling in Flytekit can be seen in this discussion and this GitHub issue.
Would you like more details on how to potentially work around this issue or further insights into similar reported problems?
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!
We're also seeing this, even on latest commit https://github.com/flyteorg/flytekit/commit/daeff3f5f0f36a1a9a1f86c5e024d1b76cdfd5cb
Note: this only happens on remote executions of a launchplan, I cannot reproduce locally.
Reopening to double-check what's happening.
Reopening to double-check what's happening.
Sorry, just tested once again, and I think it's actually resolved. I had pointed to the wrong registration version while testing, I'm sorry π
No worries, @ggydush ! It's always good to make sure things make sense.
Describe the bug
Flytekit version: v1.12.2 When triggering a remote LaunchPlan execution, Flytekit is unable to process certain output types. In our tests we're getting the following error.
Expected behavior
Outputs should be properly returned.
Additional context to reproduce
Trigger a remote launchplan that returns
<FlyteLiteral(Literal) scalar { generic { fields { key: "error" value { null_value: NULL_VALUE } } } }>
this won't have themetadata
field set and in turn fail to process.We believe this bug was introduced with the following PR
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?