Open
Description
Description
After this PR #24651, ray list tasks is able to display "RUNNING" state. However, this status is not available from ray memory.
The root problem is that "RUNNING" state is only available from the "execution side", but ray memory is only processing the state from the owner (caller) side, which cannot figure out if tasks is actually executing or not.
ray list tasks solves this problem by processing states from both caller and execution side (as you can see from the PR). We should do the same thing for ray memory to reach the parity.
Use case
No response