Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[core] Mark run_function_on_all_workers as deprecated until we get rid of this. #29062

Merged
merged 2 commits into from
Oct 5, 2022

Conversation

fishbone
Copy link
Contributor

@fishbone fishbone commented Oct 4, 2022

Signed-off-by: Yi Cheng [email protected]

Why are these changes needed?

run_function_on_all_workers has a lot of issues:

  • no guarantee that the function run before the remote function run.
  • pubsub signal might be lost in some failure cases.

We can't delete it for now because the working dir init depends on this. So mark it as deprecated to warn people who uses this and delete it once we fix the working dir.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: Yi Cheng <[email protected]>
@scv119
Copy link
Contributor

scv119 commented Oct 4, 2022

do we know who is using it?

@@ -683,6 +683,7 @@ def get_objects(self, object_refs: list, timeout: Optional[float] = None):
debugger_breakpoint,
)

@Deprecated
Copy link
Contributor

Choose a reason for hiding this comment

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

can we add some comments explain why it's deprecated? (as what you put in the PR summary)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure!

@fishbone
Copy link
Contributor Author

fishbone commented Oct 4, 2022

@scv119 as far as I know, no one is using that. Modin has moved away from using this.

Signed-off-by: Yi Cheng <[email protected]>
@rkooo567
Copy link
Contributor

rkooo567 commented Oct 5, 2022

Does it make sense to deprecate it when this was never public APi?

@fishbone
Copy link
Contributor Author

fishbone commented Oct 5, 2022

Does it make sense to deprecate it when this was never public APi?

  1. This is never public API. It's in ray/_private
  2. Some developers might just use this. For example, data set tries to use this for customized SerDe.

I think this is just to double warn the people who want to go to the dangerous zones not to do this.

@fishbone fishbone merged commit 3cd442a into ray-project:master Oct 5, 2022
WeichenXu123 pushed a commit to WeichenXu123/ray that referenced this pull request Dec 19, 2022
…rid of this. (ray-project#29062)

run_function_on_all_workers has a lot of issues:

no guarantee that the function run before the remote function run.
pubsub signal might be lost in some failure cases.
We can't delete it for now because the working dir init depends on this. So mark it as deprecated to warn people who uses this and delete it once we fix the working dir.

Signed-off-by: Weichen Xu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants