Skip to content

Conversation

@Sparks0219
Copy link
Contributor

Description

Briefly describe what this PR accomplishes and why it's needed.

Making Cancel Remote Task RPC idempotent and fault tolerant. Added a python test to verify retry behavior, no cpp test since it just calls CancelTask RPC so nothing to test. Also renamed uses of RemoteCancelTask to CancelRemoteTask since it should be consistent.

@Sparks0219 Sparks0219 requested a review from a team as a code owner October 21, 2025 21:40
@Sparks0219 Sparks0219 added the go add ONLY when ready to merge, run all tests label Oct 21, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request makes the CancelRemoteTask RPC fault-tolerant and idempotent, which is a great improvement for robustness. The related renames from RemoteCancelTask to CancelRemoteTask improve consistency across the codebase. The addition of a Python test to verify the retry behavior is also a valuable contribution. The changes are well-implemented, but I found one issue in a fake client implementation that needs to be addressed.

Signed-off-by: joshlee <[email protected]>
Signed-off-by: joshlee <[email protected]>
@ray-gardener ray-gardener bot added the core Issues that should be addressed in Ray Core label Oct 22, 2025
Copy link
Collaborator

@edoakes edoakes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but the naming is still a little misleading. Should we encode the ownership semantic? For example, CancelOwnedTask or CancelTaskOnOwner. I don't love either of those, but you get the gist.

@edoakes edoakes merged commit e120b85 into ray-project:master Oct 22, 2025
6 checks passed
@edoakes
Copy link
Collaborator

edoakes commented Oct 22, 2025

(can rename in separate PR as desired)

xinyuangui2 pushed a commit to xinyuangui2/ray that referenced this pull request Oct 27, 2025
> Briefly describe what this PR accomplishes and why it's needed.

Making Cancel Remote Task RPC idempotent and fault tolerant. Added a
python test to verify retry behavior, no cpp test since it just calls
CancelTask RPC so nothing to test. Also renamed uses of RemoteCancelTask
to CancelRemoteTask since it should be consistent.

---------

Signed-off-by: joshlee <[email protected]>
Signed-off-by: xgui <[email protected]>
landscapepainter pushed a commit to landscapepainter/ray that referenced this pull request Nov 17, 2025
> Briefly describe what this PR accomplishes and why it's needed.

Making Cancel Remote Task RPC idempotent and fault tolerant. Added a
python test to verify retry behavior, no cpp test since it just calls
CancelTask RPC so nothing to test. Also renamed uses of RemoteCancelTask
to CancelRemoteTask since it should be consistent.

---------

Signed-off-by: joshlee <[email protected]>
Aydin-ab pushed a commit to Aydin-ab/ray-aydin that referenced this pull request Nov 19, 2025
> Briefly describe what this PR accomplishes and why it's needed.

Making Cancel Remote Task RPC idempotent and fault tolerant. Added a
python test to verify retry behavior, no cpp test since it just calls
CancelTask RPC so nothing to test. Also renamed uses of RemoteCancelTask
to CancelRemoteTask since it should be consistent.

---------

Signed-off-by: joshlee <[email protected]>
Signed-off-by: Aydin Abiar <[email protected]>
Future-Outlier pushed a commit to Future-Outlier/ray that referenced this pull request Dec 7, 2025
> Briefly describe what this PR accomplishes and why it's needed.

Making Cancel Remote Task RPC idempotent and fault tolerant. Added a
python test to verify retry behavior, no cpp test since it just calls
CancelTask RPC so nothing to test. Also renamed uses of RemoteCancelTask
to CancelRemoteTask since it should be consistent.

---------

Signed-off-by: joshlee <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Issues that should be addressed in Ray Core go add ONLY when ready to merge, run all tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants