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] [Docs] Align file names in getting_started.md #36800

Merged
merged 3 commits into from
Jun 27, 2023

Conversation

JungeAlexander
Copy link
Contributor

@JungeAlexander JungeAlexander commented Jun 25, 2023

Why are these changes needed?

While running through the getting started tutorial for Ray Serve, I was confused by the mismatch of the file names mentioned in the markdown explanations and the file names stated in the first line of the imported source files.
This fixes the mismatch by matching file names listed at the top of doc/source/serve/doc_code/getting_started/model_deployment_full.py and doc/source/serve/doc_code/getting_started/model_graph.py to the file names mentioned in the tutorial (serve_quickstart.py and serve_quickstart_composed.py, respectively).

Related issue number

None.

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 added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • 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 :(

While running throught the tutorial
(https://docs.ray.io/en/latest/serve/getting_started.html#getting-started),
I was confused by the mismatch of the file names mentioned
in the markdown explanations and the file names stated in
the first line of the imported source files.
This tries to fix the mismatch by changing the markdown. Alternatively, the imported source files could be changed.

Signed-off-by: Alexander Junge <alexander.junge@gmail.com>
Copy link
Contributor

@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.

Thanks so much for the fix!

I prefer the names that were in the console commands. Do you mind flipping it to update the file names to match serve_quickstart and serve_quickstart_composed instead?

This reverts commit a203421.

Signed-off-by: Alexander Junge <alexander.junge@gmail.com>
Adjust file names to match serve_quickstart and serve_quickstart_composed

Signed-off-by: Alexander Junge <alexander.junge@gmail.com>
@JungeAlexander
Copy link
Contributor Author

Thanks so much for the fix!

I prefer the names that were in the console commands. Do you mind flipping it to update the file names to match serve_quickstart and serve_quickstart_composed instead?

@edoakes thanks for the feedback and no problem at all - I did just that.

@JungeAlexander JungeAlexander requested a review from edoakes June 27, 2023 18:55
@edoakes edoakes merged commit bf17bf4 into ray-project:master Jun 27, 2023
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
)

While running through the [getting started tutorial](https://docs.ray.io/en/latest/serve/getting_started.html#getting-started) for Ray Serve, I was confused by the mismatch of the file names mentioned in the markdown explanations and the file names stated in the first line of the imported source files.
This fixes the mismatch by matching file names listed at the top of `doc/source/serve/doc_code/getting_started/model_deployment_full.py` and `doc/source/serve/doc_code/getting_started/model_graph.py` to the file names mentioned in the tutorial (`serve_quickstart.py` and `serve_quickstart_composed.py`, respectively).

Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
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.

2 participants