[BUG] rshift '>>' operator doesn't work properly with remoteEntities about flyte HOT 4 CLOSED

cc @pingsutw

from flyte.

The issue you are describing is related to the improper functioning of the >> operator with remote entities in Flyte. This problem has been noted in various contexts, including chaining tasks and workflows. According to this discussion, chaining a task with a remote task that doesn't have outputs doesn't work correctly. Additionally, another discussion highlights issues with the >> operator in different scenarios. Furthermore, a related GitHub issue discusses the order of execution not being respected when running locally.

Would you like more detail on how to work around this issue or any other specific aspect?

Sources:

• Hi everyone I want to report a possible issue that I ve dete
• I have found a peculiar case where I can not successfully re
• GitHub Issue #3644

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!

from flyte.

@andresgomezfrr Could you provide an example like the one you have just mentioned?

remote_entity_1.output1.ref.node >> remote_entity_2.output1.ref.node

from flyte.

I tested this again with the latest release and looks like it is working fine, I'm going to close this issue

from flyte.