dev/openfuyao-2.48.0

openFuyao-bot调整 xgrammar 版本，修复漏洞

be4152b6创建于 2025年9月12日历史提交

文件	最后提交记录	最后更新时间
_ext	[doc] Fix color of button icon and text in dark mode button (#43267) fixes the color of some icons and text on the ray-overview/use-cases page, which is currently unreadable in the dark theme. This fix became slightly more complex because the icon was originally put in place using a pseudo-element, and you can't apply CSS styles that way. So instead, we improved the sphinx extension we use to create URL query parameters to make sure it parses content nested inside as usual (before it would treat any text nested inside as just text). This makes the query parameter extension machinery more useful and more robust. --------- Signed-off-by: pdmurray <peynmurray@gmail.com> Signed-off-by: Peyton Murray <peynmurray@gmail.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com>	2 年前
_includes	[docs; RLlib] Remove "new API stack" banner from all RLlib docs pages as its now the default. (#54282)	1 年前
_static	use gtm datalayer directly, fix format (#54144)	1 年前
_templates	Update google tag container id (#54444) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> We don't have access to the previous tag manager and can't edit event collection. This new one works <!-- 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: Vignesh Hirudayakanth <vigneshkanth@gmail.com>	1 年前
cluster	[Docs] Troubleshooting DeepSeek/multi-node GPU deployment on KubeRay (#54229) Signed-off-by: Seiji Eicher <seiji@anyscale.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com>	1 年前
data	[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 年前
images	[data] Integrate Ray Dataset with Daft Dataframe (#51531) <!-- 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? This adds nice integrations between Daft and Ray Data along with: Unit test for data round-trip (including more interesting types such as a Tensor) Documentation Implementation on Ray Dataset for conversion to/from Daft Dataframes ## Related issue number Re-opening #50630 which was borked by a bad rebase. ## 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. - [x] I've included any doc changes needed for https://docs.ray.io/en/master/. - [x] 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 - [x] Unit tests - [ ] Release tests - [ ] This PR is not tested :( --------- Signed-off-by: Jay Chia <17691182+jaychia@users.noreply.github.com> Signed-off-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Richard Liaw <rliaw@berkeley.edu>	1 年前
llm	[ray.data.llm] s/model/model_source for vLLMEngineProcessorConfig (#52104) <!-- 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? The field name should have been changed as of 2.44. Applying the same change as https://github.com/ray-project/ray/pull/51042 <!-- 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. - [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 - [x] Release tests - [ ] This PR is not tested :( Signed-off-by: Linkun Chen <github@lkchen.net>	1 年前
ray-air	[serve] remove GPT-J example (#42243) Signed-off-by: Matthew Deng <matt@anyscale.com>	2 年前
ray-contribute	Cursor - Update ray docs Twitter link to X (#54238) Generated via Cursor Background Agents --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>	1 年前
ray-core	[doc][core] fix reStructuredText formatting on Resources page (#53882) reStructuredText doesn't support nested inline markup like bold and monospace at the same time. So we move the double backticks outside of the bold markup. currently looks like https://docs.ray.io/en/latest/ray-core/scheduling/resources.html#specifying-node-resources <img width="707" alt="image" src="https://github.com/user-attachments/assets/8ea43328-24f8-4591-a58e-65df53eecb18" /> Signed-off-by: David Xia <david@davidxia.com>	1 年前
ray-more-libs	[Collective] Ray 集合通信库支持昇腾 HCCL 后端 Co-authored-by: fivezehua<wuzehua2@huawei.com>	1 年前
ray-observability	[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 年前
ray-overview	调整 xgrammar 版本，修复漏洞 Co-authored-by: liuxh25<liuxianghai1@huawei.com>	10 个月前
ray-references	[Doc] Fix broken references in Ray Core documentation (#45115) Signed-off-by: pdmurray <peynmurray@gmail.com>	2 年前
ray-security	[Docs] Add contraction in doc/source/ray-security/index.md (#50204) ## 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: Tyler Freckmann <tfreckmann@anyscale.com> Co-authored-by: Tyler Freckmann <tfreckmann@anyscale.com>	1 年前
rllib	[RLlib] Enhance ConnectorV2 ObservationPreprocessor APIs (add multi-agent support; add episode arg). (#54209)	1 年前
serve	[Docs] Troubleshooting DeepSeek/multi-node GPU deployment on KubeRay (#54229) Signed-off-by: Seiji Eicher <seiji@anyscale.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com>	1 年前
templates	[漏洞修复] 调整 Torch, Transformers 及前端依赖库版本修复漏洞 Co-authored-by: liuxianghai1<liuxianghai1@huawei.com>	11 个月前
train	[漏洞修复] 调整 Torch, Transformers 及前端依赖库版本修复漏洞 Co-authored-by: liuxianghai1<liuxianghai1@huawei.com>	11 个月前
tune	add object detection notebooks (#50965)	1 年前
conf.py	[core] Fix ActorClass.remote return typing and expose Actor class methods to static analysis (#53986) <!-- 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? Changes in this PR are inspired by https://github.com/zen-xu/sunray Calling remote() on an Actor class incorrectly returns an ObjectRef[...] type. Also, the Actor class's methods are not available to IDEs, as the type is incorrect. This PR makes ActorHandle a generic type ActorHandle[T] and also creates an type alias: ActorProxy = Union["ActorHandle[T]", type[T]] to expose the method signatures from the Actor class. Here are some other possible candidates for the type name instead of ActorProxy from claude: ActorInterface TypedActorHandle RemoteActorType ActorProxy ActorT cc @richardliaw @pcmoritz We'll add better type hints for actor methods in a follow up PR. The following are screenshots demonstrating the type hints in Cursor before and after this PR: **Before this PR**    --- **After this PR**    ## 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. - [ ] 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: will.lin <will.lin@anyscale.com> Signed-off-by: Philipp Moritz <pcmoritz@gmail.com> Co-authored-by: Philipp Moritz <pcmoritz@gmail.com>	1 年前
custom_directives.py	[Doc][Serve][LLM] Add doc for deploying DeepSeek (#52592) Signed-off-by: Rui Qiao <ruisearch42@gmail.com> Signed-off-by: Rui Qiao <161574667+ruisearch42@users.noreply.github.com> Co-authored-by: Gene Der Su <gdsu@ucdavis.edu>	1 年前
index.rst	Entity recognition with LLMs (#52342) <!-- 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: GokuMohandas <gokumd@gmail.com> Signed-off-by: Goku Mohandas <gokumd@gmail.com> Signed-off-by: angelinalg <angelina@anyscale.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Co-authored-by: angelinalg <angelina@anyscale.com>	1 年前
navbar.yml	[Doc] Revamp example gallery (#42862) updates the docs build system to change the way the example gallery is created. - Examples are now specified in yaml format, regularizing the metadata for each example in each ray library - Each ray library has an example page that is constructed from its corresponding yaml data - The example gallery itself is built using all ray library example yaml input data, meaning that individual ray library example pages no longer get out of sync with what is in the example gallery - As a result of changing the way that ray libraries store their examples, I had to change many of the the references to the ray library examples pages. The content of the example pages has not been changed. These changes are responsible for the majority of the files touched here. - A second impact of the changes here is that because some of the example pages were being included in toctrees before and now they are not, is that they need to be marked as orphaned. This has been done where necessary, but in particular in the .ipynb files this is actually done in the metadata of the file. - Capitalize "Example Gallery" in the top navigation bar --------- Signed-off-by: pdmurray <peynmurray@gmail.com> Co-authored-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com>	2 年前
preprocess_github_markdown.py	Remove unnecessary string literal splits (#47360) I found there were a bunch. Found them with: bash find -name '*.py' -exec grep --color=always -HnIie '".*" ".*"' {} \; | less -r --------- Signed-off-by: Santiago Castro <santiagoc@netflix.com> Signed-off-by: Santiago Castro <bryant1410@gmail.com>	1 年前
robots.txt	[Doc] Limit search engine crawler indexing to latest and master (#31214)	3 年前