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
The issue you're encountering with the Flyte UI showing a TypeError when using approve in a dynamic workflow with overridden node names is likely related to known limitations and bugs in handling node name overrides, especially in dynamic contexts. According to this discussion and this GitHub issue, long node names or specific characters in node names can cause unexpected behavior in the Flyte UI.
To avoid this issue, you can either:
Avoid using underscores in node names, as they are known to cause issues (source).
Keep node names under 20 characters to prevent them from being hashed (source).
Would you like more details on how to handle node name overrides or any other aspect of Flyte?
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!
eapolinario
added
backlogged
For internal use. Reserved for contributor team workflow.
and removed
untriaged
This issues has not yet been looked at by the Maintainers
labels
Aug 8, 2024
Describe the bug
Summary
TypeError: Cannot read properties of undefined (reading 'id')
when subworkflow node_name is overriddensubworkflow(v=i).with_overrides(node_name=f"subworkflow_{i}")
to justsubworkflow(v=i)
Expected behavior
Additional context to reproduce
Sample code to reproduce example:
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: