[BUG] RemoteEntities doesn't work properly using >>

[andresgomezfrr]

Describe the bug

I'm getting this error:

  'Output' object has no attribute 'ref'

The internal code where this is thrown is:

flytekit/core/promise.py:850 in __rshift__                       
│                                                                              │
│    847 │   │   return self._ref                                              │
│    848 │                                                                     │
│    849 │   def __rshift__(self, other: Union[Promise, VoidPromise]):         │
│ ❱  850 │   │   if self.ref and other.ref:                                    │
│    851 │   │   │   self.ref.node.runs_before(other.ref.node)                 │
│    852 │   │   return other        

I think the issue is that this class Output:

https://github.com/flyteorg/flytekit/blob/master/flytekit/core/promise.py#L697-L716

doesnt have implemented the ref, so when you try to use the >> operator using remoteEntity which are wrapped in the Output class you will hit this error.

If I check the type of my remoteEntity it is <class 'flytekit.core.promise.create_task_output.<locals>.Output'>

a >> remoteEntity(this is an Output class) > b

This is a workaround:

a >> remoteEntity.<some_field>.node > b

This is related to: #5393

Expected behavior

Be able to chaining remoteEntities

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

The issue you're encountering 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 GitHub issue, the >> operator does not work properly with remote entities, leading to the error 'Output' object has no attribute 'ref'.

A workaround for this issue is to reference the specific field of the remote entity's output, as shown below:

a >> remoteEntity.<some_field>.node >> b

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

Sources:

• GitHub Issue #5393
• GitHub Issue #3100

---

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!

[Mecoli1219]

@eapolinario Are you working on this issue? I think I have some thoughts that may solve this issue.

[Mecoli1219]

Hi @andresgomezfrr, could you please share a concrete example that reproduces the error? That would greatly help in pinpointing the issue.

[eapolinario]

@Mecoli1219 , I'm not actively working on this. I unassigned myself.