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] http_options only works in the first serve.start call #17577

Closed
simon-mo opened this issue Aug 4, 2021 · 3 comments
Closed

[Serve] http_options only works in the first serve.start call #17577

simon-mo opened this issue Aug 4, 2021 · 3 comments
Labels
bug Something that is supposed to be working; but isn't P2 Important issue, but not time-critical serve Ray Serve Related Issue
Milestone

Comments

@simon-mo
Copy link
Contributor

simon-mo commented Aug 4, 2021

http_options cannot be updated at subsequent serve.start that act as connect calls.

@simon-mo simon-mo added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Aug 4, 2021
@simon-mo
Copy link
Contributor Author

simon-mo commented Aug 4, 2021

this can be closed by #15820 if it supports updated as well @edoakes

@stale
Copy link

stale bot commented Dec 3, 2021

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

  • If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
  • If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

@stale stale bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Dec 3, 2021
@stale
Copy link

stale bot commented Dec 17, 2021

Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.

Please feel free to reopen or open a new issue if you'd still like it to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for opening the issue!

@stale stale bot closed this as completed Dec 17, 2021
@edoakes edoakes reopened this Jan 6, 2022
@stale stale bot removed the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Jan 6, 2022
@shrekris-anyscale shrekris-anyscale added P2 Important issue, but not time-critical serve Ray Serve Related Issue and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Jan 6, 2022
@shrekris-anyscale shrekris-anyscale added this to the Serve backlog milestone Jan 6, 2022
@edoakes edoakes removed the platform label Apr 25, 2022
@edoakes edoakes closed this as completed Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't P2 Important issue, but not time-critical serve Ray Serve Related Issue
Projects
None yet
Development

No branches or pull requests

4 participants