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

[Serve] Remove the warning for async handles in 2.0 #27346

Merged
merged 1 commit into from
Aug 2, 2022

Conversation

simon-mo
Copy link
Contributor

@simon-mo simon-mo commented Aug 1, 2022

Why are these changes needed?

This PR removes the warning about using sync handles in async context (common) and using async handle in sync context (rare). In Serve 2.0, we are helping user to inject the handles via .bind API. However, the only handles we are injecting right now is SyncHandle due to technical limitation. Therefore we want to remove this non-actionable warnings.

Related issue number

Closes #27266

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 :(

@edoakes edoakes merged commit a9d94f7 into ray-project:master Aug 2, 2022
simon-mo added a commit to simon-mo/ray that referenced this pull request Aug 7, 2022
gramhagen pushed a commit to gramhagen/ray that referenced this pull request Aug 15, 2022
gramhagen pushed a commit to gramhagen/ray that referenced this pull request Aug 15, 2022
Stefan-1313 pushed a commit to Stefan-1313/ray_mod that referenced this pull request Aug 18, 2022
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.

[Serve] Simple multi-deployment example prints warning about sync handle in asyncio loop
3 participants