dev/openfuyao-2.48.0

文件	最后提交记录	最后更新时间
doc_code	Make it possible to use Ray distributed debugger without setting RAY_DEBUG (#48301) <!-- 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 in order to use the distributed debugger, the user has to set RAY_DEBUG=1. This has two disadvantages: 1. It is disruptive to the workflow and much more overhead than just adding the breakpoint() instruction and re-running the program (since the runtime environment has to be updated and the user needs to make sure that the driver uses the flag too e.g. by restarting the python kernel or in the worst case the container). 2. It is very easy to forget this step and then get the impression that the debugger is not working. There is no reason to require RAY_DEBUG=1 to be set (the CLI debugger works without the flag too and in particular the flag has no impact on performance unless the debugger is actually entered). The reason this flag was originally introduced was as a feature flag to switch between the CLI debugger and the UI debugger. Now that the UI debugger is getting more mature, it is better to make it the default and let people who want to use the CLI debugger use a RAY_DEBUG=legacy flag. This PR also renames the RAY_PDB flag to RAY_DEBUG_POST_MORTEM and unifies the usage of the flag between the old and new debugger (in particular, with the new debugger, post mortem debugging is now off unless the user activates it). ## 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: Philipp Moritz <pcmoritz@gmail.com>	1 年前
images	[Debugger] Clarify that only one paused task can be debugged at a time (#48415) <!-- 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? I was initially confused that I couldn't join another paused task while a debugger was in "continue" mode. ## 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: Philipp Moritz <pcmoritz@gmail.com> Co-authored-by: bhuang <bhuang@anyscale.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com>	1 年前
reference	[Docs] Standardize on all-caps NVIDIA (#53183) Vale currently throws an error if you use "NVIDIA" instead of "Nvidia" but actually we should be using all-caps NVIDIA: This PR updates the Vale vocab and fixes the spelling across the repo. Signed-off-by: Ricardo Decal <rdecal@anyscale.com>	1 年前
user-guides	Fix typos (#53048) Signed-off-by: omahs <73983677+omahs@users.noreply.github.com>	1 年前
getting-started.rst	Fix typos in doc directory (#51054) Signed-off-by: co63oc <co63oc@users.noreply.github.com>	1 年前
index.md	docs: ray distributed debugger (#45913) ## Why are these changes needed? Introduce ray distributed debugger docs and also the form for downloading the debugger. 	2 年前
key-concepts.rst	[docs] Add Nsight system docs on Ray (#40396) Add Ray documentation for new natively supported Nsight Profiler feature	2 年前
ray-distributed-debugger.rst	[Doc] clarify the ide support for distributed debugger (#50962) <!-- 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 - [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. - [ ] 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: Huaiwei Sun <scottsun94@gmail.com>	1 年前