| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[Data] Add reading from Delta Lake tables and from Unity Catalog (#53701) ## Why are these changes needed? The current methods for accessing data within Databricks is limited in scalability and governance features. This allows for large scale reads from Databricks that also integrates with Unity Catalog using credential vending. --------- Signed-off-by: soffer-anyscale <stephen.offer@anyscale.com> Signed-off-by: soffer-anyscale <173827098+soffer-anyscale@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Alexey Kudinkin <ak@anyscale.com> | 1 年前 | |
[data] replace np.array to np.asarray (#52851) replace some np.array to np.asarray to avoid unnecessary copies Signed-off-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[docs] displaying image with show() (#53155) fix for issue flagged here: https://github.com/ray-project/ray/issues/52674: Issue showing image Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com> | 1 年前 | |
[data/docs] Key Concepts Page (#50129) ## Why are these changes needed? Refresher for https://github.com/ray-project/ray/pull/50022, but on a separate page and a bit more holistic. It's not tightly integrated into the other pages yet but I will do a revision of quickstart/overview/data.rst pages. ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Balaji Veeramani <bveeramani@berkeley.edu> | 1 年前 | |
[data/llm/docs] Initial draft of user guide for Data LLM APIs (#50674) ## Why are these changes needed? Adds user guide and link-ins for Ray Data documentation. This is part of the #50639 thread of work. This is based on #50494 cc @comaniac @gvspraveen @kouroshHakha ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Cody Yu <hao.yu.cody@gmail.com> | 1 年前 | |
[doc] data: update bento ml link (#52359) the blog post on bento ml website no longer exists.. this youtube link is the best next thing that on the Internet right now Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[Doc] Run pre-commit on data docs (#47341) ## Why are these changes needed? Currently we have no linting on any part of the docs code. This PR runs pre-commit on the data docs. This PR fixes the following issues: ` trim trailing whitespace.................................................Failed - hook id: trailing-whitespace - exit code: 1 - files were modified by this hook Fixing doc/source/data/saving-data.rst Fixing doc/source/data/performance-tips.rst Fixing doc/source/data/loading-data.rst Fixing doc/source/data/batch_inference.rst Fixing doc/source/data/api/grouped_data.rst Fixing doc/source/data/custom-datasource-example.rst Fixing doc/source/data/execution-configurations.rst Fixing doc/source/data/data-internals.rst fix end of files.........................................................Failed - hook id: end-of-file-fixer - exit code: 1 - files were modified by this hook Fixing doc/source/data/saving-data.rst Fixing doc/source/data/images/dataset-pipeline-2-mini.svg Fixing doc/source/data/images/dataset-loading-1.svg Fixing doc/source/data/monitoring-your-workload.rst Fixing doc/source/data/images/dataset-repeat-2.svg Fixing doc/source/data/images/dataset-pipeline-2.svg Fixing doc/source/data/images/dataset-read.svg Fixing doc/source/data/images/dataset-arch.svg Fixing doc/source/data/user-guide.rst Fixing doc/source/data/images/dataset-shuffle.svg Fixing doc/source/data/execution-configurations.rst Fixing doc/source/data/images/air-preprocessor.svg Fixing doc/source/data/images/MongoDB_Logo.svg Fixing doc/source/data/images/preprocessors.svg Fixing doc/source/data/images/dataset-pipeline-3.svg Fixing doc/source/data/images/dataset-pipeline-1.svg Fixing doc/source/data/examples/images/batch-training.svg Fixing doc/source/data/images/dataset-spill.svg Fixing doc/source/data/images/dataset-map.svg Fixing doc/source/data/images/dataset-repeat-1.svg check for added large files..............................................Passed check python ast.........................................................Passed check json...............................................................Passed check toml...........................................(no files to check)Skipped black....................................................................Passed flake8...................................................................Passed prettier.............................................(no files to check)Skipped mypy.................................................(no files to check)Skipped isort (python)...........................................................Passed rst directives end with two colons.......................................Passed rst inline code next to normal text..................................Passed use logger.warning(......................................................Passed check for not-real mock methods..........................................Passed ShellCheck v0.9.0....................................(no files to check)Skipped clang-format.........................................(no files to check)Skipped Google Java Formatter................................(no files to check)Skipped Check for Ray docstyle violations........................................Passed Check for Ray import order violations....................................Passed ` Signed-off-by: pdmurray <peynmurray@gmail.com> Co-authored-by: Cuong Nguyen <128072568+can-anyscale@users.noreply.github.com> | 1 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[doc] data: update broken link (#52332) change link to youtube video Signed-off-by: Lonnie Liu <lonnie@anyscale.com> | 1 年前 | |
[Data] Hide Data-Juicer example from documentation (#52441) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> The Data-Juicer example doesn't illustrate how to use Ray Data. So, it doesn't belong in the Ray Data examples. This PR moves it to the "More libraries" section. ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu> | 1 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[data] fix working code snippets (#52748) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: jhsu <jhsu@anyscale.com> | 1 年前 | |
[Data] [Docs] Consolidate shuffling-related information into Shuffling Data page (#44098) Consolidate shuffling-related information spread out across Ray Data docs into a new Shuffling Data page. Signed-off-by: Scott Lee <sjl@anyscale.com> | 2 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[doc] updating dead links (#53573) Updating most of the links failing in the sphinx linkcheck job https://buildkite.com/ray-project/postmerge/builds/10631#01973c8e-a289-4699-8fa1-90db667c591e <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com> | 1 年前 | |
[Data] [Docs] Add docs section for Ray Data progress bars (#47804) ## Why are these changes needed? Adds a section under the Monitoring Your Workload docs page, going over progress bar interpretation and configuration. New section: https://anyscale-ray--47804.com.readthedocs.build/en/47804/data/monitoring-your-workload.html#ray-data-progress-bars ## Related issue number Followup PR to https://github.com/ray-project/ray/pull/47692. ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR. - [x] I've run scripts/format.sh to lint the changes in this PR. - [x] 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. - [x] 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: Scott Lee <sjl@anyscale.com> | 1 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[doc] updating dead links (#53573) Updating most of the links failing in the sphinx linkcheck job https://buildkite.com/ray-project/postmerge/builds/10631#01973c8e-a289-4699-8fa1-90db667c591e <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com> | 1 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[data] Fix formatting, improve documentation, make finalize public (#52761) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? Currently the rendering is a bit odd: <img width="939" alt="Screenshot 2025-05-02 at 5 19 40 PM" src="https://github.com/user-attachments/assets/4f8ca220-b9cd-4858-ba5d-d22cb71c9b60" /> ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Alexey Kudinkin <alexey.kudinkin@gmail.com> | 1 年前 | |
[Docs] Added user-guide for Joins (#52987) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? 1. Added user-guide for joins 2. Added sections on different shuffling implementations available in Ray Data 3. Tidying up ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[data] replace np.array to np.asarray (#52851) replace some np.array to np.asarray to avoid unnecessary copies Signed-off-by: Hao Chen <chenh1024@gmail.com> | 1 年前 | |
[Doc][LLM] add VLM example to doc (#53018) Signed-off-by: Linkun <github@lkchen.net> | 1 年前 | |
[Data] [Docs] Prose and formatting updates (Working with Tensors / Working with PyTorch pages) (#43992) Prose and formatting updates for the following docs pages: - Working with Tensors (renamed to Working with Tensors / NumPy) - [PR version](https://anyscale-ray--43992.com.readthedocs.build/en/43992/data/working-with-tensors.html) - Working with PyTorch - [PR version](https://anyscale-ray--43992.com.readthedocs.build/en/43992/data/working-with-pytorch.html) Signed-off-by: Scott Lee <sjl@anyscale.com> | 2 年前 | |
[data] fix working code snippets (#52748) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> ## Related issue number <!-- For example: "Closes #1234" --> ## 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 :( --------- Signed-off-by: jhsu <jhsu@anyscale.com> | 1 年前 | |
[Data] user column names read api doc changes (#52587) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> Allows users to manipulate the column output names ## Related issue number Closes https://github.com/ray-project/ray/issues/52282 <!-- For example: "Closes #1234" --> ## Checks - [ ] I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR. - [x] 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: jhsu <jhsu@anyscale.com> Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Signed-off-by: Justin Yu <justinvyu@anyscale.com> Signed-off-by: Rui Qiao <ruisearch42@gmail.com> Signed-off-by: Alex Wu <c.alexwu@gmail.com> Signed-off-by: Kai-Hsun Chen <kaihsun@anyscale.com> Signed-off-by: can <can@anyscale.com> Signed-off-by: Hao Chen <chenh1024@gmail.com> Signed-off-by: Lonnie Liu <lonnie@anyscale.com> Signed-off-by: Srinath Krishnamachari <srinath.krishnamachari@anyscale.com> Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu> Signed-off-by: Balaji Veeramani <balaji@anyscale.com> Signed-off-by: Alexey Kudinkin <ak@anyscale.com> Signed-off-by: irabbani <irabbani@anyscale.com> Signed-off-by: dayshah <dhyey2019@gmail.com> Signed-off-by: Arthur <atte.book@gmail.com> Signed-off-by: Rui Qiao <161574667+ruisearch42@users.noreply.github.com> Signed-off-by: fscnick <fscnick.dev@gmail.com> Signed-off-by: abrar <abrar@anyscale.com> Signed-off-by: lkchen <github@lkchen.net> Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com> Signed-off-by: kevin <kevin@anyscale.com> Signed-off-by: Xingyu Long <xingyulong97@gmail.com> Signed-off-by: Chi-Sheng Liu <chishengliu@chishengliu.com> Signed-off-by: Linkun Chen <github@lkchen.net> Signed-off-by: Josh Karpel <josh.karpel@gmail.com> Signed-off-by: Kourosh Hakhamaneshi <kourosh@anyscale.com> Signed-off-by: kourosh hakhamaneshi <31483498+kouroshHakha@users.noreply.github.com> Signed-off-by: Sophie <sophy010017@gmail.com> Signed-off-by: Matthew Deng <matt@anyscale.com> Signed-off-by: Matthew Owen <mowen@anyscale.com> Signed-off-by: Gene Su <e870252314@gmail.com> Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com> Co-authored-by: Justin Yu <justinvyu@anyscale.com> Co-authored-by: Rui Qiao <161574667+ruisearch42@users.noreply.github.com> Co-authored-by: Alex Wu <66259759+popojk@users.noreply.github.com> Co-authored-by: Kai-Hsun Chen <kaihsun@anyscale.com> Co-authored-by: Saihajpreet Singh <c-saihajpreet.singh@anyscale.com> Co-authored-by: Cuong Nguyen <128072568+can-anyscale@users.noreply.github.com> Co-authored-by: Hao Chen <chenh1024@gmail.com> Co-authored-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com> Co-authored-by: srinathk10 <68668616+srinathk10@users.noreply.github.com> Co-authored-by: Balaji Veeramani <balaji@anyscale.com> Co-authored-by: Ziyi Tan <ajb459684460@gmail.com> Co-authored-by: Alexey Kudinkin <ak@anyscale.com> Co-authored-by: Ibrahim Rabbani <irabbani@anyscale.com> Co-authored-by: Dhyey Shah <dhyey2019@gmail.com> Co-authored-by: Arthur Böök <atte.book@gmail.com> Co-authored-by: Gene Der Su <gdsu@ucdavis.edu> Co-authored-by: Sven Mika <svenmika1977@gmail.com> Co-authored-by: fscnick <6858627+fscnick@users.noreply.github.com> Co-authored-by: Abrar Sheikh <abrar@anyscale.com> Co-authored-by: simonsays1980 <simon.zehnder@gmail.com> Co-authored-by: lkchen <github@lkchen.net> Co-authored-by: Jiajun Yao <jeromeyjj@gmail.com> Co-authored-by: Kevin H. Luu <kevin@anyscale.com> Co-authored-by: Christopher Zhang <chris@anyscale.com> Co-authored-by: Xingyu Long <xingyulong97@gmail.com> Co-authored-by: Chi-Sheng Liu <chishengliu@chishengliu.com> Co-authored-by: Josh Karpel <josh.karpel@gmail.com> Co-authored-by: kourosh hakhamaneshi <31483498+kouroshHakha@users.noreply.github.com> Co-authored-by: Sophie Hsu <112261858+sophie0730@users.noreply.github.com> Co-authored-by: matthewdeng <matt@anyscale.com> Co-authored-by: Matthew Owen <mowen@anyscale.com> Co-authored-by: Lonnie Liu <lonnie@anyscale.com> Co-authored-by: Gene Der Su <e870252314@gmail.com> Co-authored-by: Balaji Veeramani <bveeramani@berkeley.edu> | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 |