Various enhancements to the Gradio Ray Serve tutorial #50276
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* adds missing pip requirements * improves the overall narrative flow of the tutorial * clarifies that there are 2 separate examples within the same page * clarifies the difference between the two methods Signed-off-by: Ricardo Decal <rdecal@anyscale.com>
crypdick
requested review from
edoakes,
zcin,
GeneDer,
akshay-anyscale and
a team
as code owners
|
@zcin to review |
jcotant1
added
serve
edoakes
approved these changes
Mar 5, 2025
Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Signed-off-by: Ricardo Decal <crypdick@users.noreply.github.com>
Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Signed-off-by: Ricardo Decal <crypdick@users.noreply.github.com>
Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Signed-off-by: Ricardo Decal <crypdick@users.noreply.github.com>
Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Signed-off-by: Ricardo Decal <crypdick@users.noreply.github.com>
Co-authored-by: Cindy Zhang <cindyzyx9@gmail.com> Signed-off-by: Ricardo Decal <crypdick@users.noreply.github.com>
abrarsheikh
pushed a commit
that referenced
this pull request
Mar 8, 2025
## Why are these changes needed? * adds missing pip requirements * improves the overall narrative flow of the tutorial * clarifies that there are 2 separate examples within the same page * clarifies the difference between the two methods ## Related issue number N/A ## Checks - [X] 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 :( --------- Signed-off-by: Ricardo Decal <rdecal@anyscale.com> Signed-off-by: Ricardo Decal <crypdick@users.noreply.github.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Co-authored-by: Cindy Zhang <cindyzyx9@gmail.com> Signed-off-by: Abrar Sheikh <abrar@anyscale.com>
elimelt
pushed a commit
to elimelt/ray
that referenced
this pull request
Mar 9, 2025
…ect#50276) ## Why are these changes needed? * adds missing pip requirements * improves the overall narrative flow of the tutorial * clarifies that there are 2 separate examples within the same page * clarifies the difference between the two methods ## Related issue number N/A ## Checks - [X] 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 :( --------- Signed-off-by: Ricardo Decal <rdecal@anyscale.com> Signed-off-by: Ricardo Decal <crypdick@users.noreply.github.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Co-authored-by: Cindy Zhang <cindyzyx9@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
Related issue number
N/A
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.