Skip to content

Issues: ray-project/ray

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Release test serve_microbenchmarks.aws failed bug Something that is supposed to be working; but isn't P0 Issues that should be fixed in short order ray-test-bot Issues managed by OSS test policy release-test release test serve Ray Serve Related Issue stability triage Needs triage (eg: priority, bug/not-bug, and owning component) weekly-release-blocker Issues that will be blocking Ray weekly releases
#50606 opened Feb 14, 2025 by can-anyscale
[core] Split giant ray core C++ targets into small ones(GCS server) core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability
#50602 opened Feb 14, 2025 by 400Ping
[core] Split giant ray core C++ targets into small ones(pubsub) core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability
#50599 opened Feb 14, 2025 by 400Ping
[core] Split giant ray core C++ targets into small ones(stats) core Issues that should be addressed in Ray Core dependencies Pull requests that update a dependency file enhancement Request for new feature and/or capability
#50588 opened Feb 14, 2025 by 400Ping
[core] Split giant ray core C++ targets into small ones core Issues that should be addressed in Ray Core dependencies Pull requests that update a dependency file enhancement Request for new feature and/or capability good-first-issue Great starter issue for someone just starting to contribute to Ray help wanted P2 Important issue, but not time-critical
#50586 opened Feb 14, 2025 by dentiny
11 tasks
[core] Cover cpplint for all C++ folders core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability good-first-issue Great starter issue for someone just starting to contribute to Ray help wanted P2 Important issue, but not time-critical
#50583 opened Feb 14, 2025 by dentiny
14 tasks
[RLlib] [Solution Found] Action masking example not working when LSTM enabled. bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50526 opened Feb 13, 2025 by JiangpengLI86
No backend type associated with device type npu bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50516 opened Feb 13, 2025 by CurtainRight
RAY_IGNORE_VERSION_MISMATCH=True has no effect on ray start --addr. bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50511 opened Feb 13, 2025 by Jay-ju
Ray's execution of the command "start --head" does not perform deduplication. bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50510 opened Feb 13, 2025 by Jay-ju
Exception: The current node timed out during startup. This could happen because some of the Ray processes failed to startup. bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50474 opened Feb 12, 2025 by Wangpc-972
[Ray Serve] Expose public interface for user to customize the router enhancement Request for new feature and/or capability serve Ray Serve Related Issue triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50465 opened Feb 12, 2025 by jectpro7
[Data] test_hudi flakes in CI 25% of the time bug Something that is supposed to be working; but isn't data Ray Data-related issues
#50463 opened Feb 12, 2025 by bveeramani
Compiled Graphs torch.Tensor serialization device bug Something that is supposed to be working; but isn't compiled-graphs core Issues that should be addressed in Ray Core triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50452 opened Feb 11, 2025 by anmscale
[serve] Unscheduleable replica shutdown is not handled gracefully bug Something that is supposed to be working; but isn't P1 Issue that should be fixed within a few weeks serve Ray Serve Related Issue
#50426 opened Feb 11, 2025 by edoakes
[Dashboard] Javascript crash on /cluster bug Something that is supposed to be working; but isn't dashboard Issues specific to the Ray Dashboard observability Issues related to the Ray Dashboard, Logging, Metrics, Tracing, and/or Profiling triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50421 opened Feb 11, 2025 by FredrikNoren
Worker Node Disconnects After 15 Seconds in Ray Cluster on AWS EC2 bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50419 opened Feb 11, 2025 by shrijayan
Fatal Python error: Floating point exception when running on H20 bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core triage Needs triage (eg: priority, bug/not-bug, and owning component)
#50418 opened Feb 11, 2025 by AkaliKong
Release test sort.regular failed bug Something that is supposed to be working; but isn't data Ray Data-related issues jailed-test Indicate that this test is jailed and will stop running in CI/CD P0 Issues that should be fixed in short order ray-test-bot Issues managed by OSS test policy release-test release test stability triage Needs triage (eg: priority, bug/not-bug, and owning component) unstable-release-test
#50417 opened Feb 11, 2025 by can-anyscale
[core] ray.remote Decorator's Return Type Cannot Be Determined by Type Checkers bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core P1 Issue that should be fixed within a few weeks usability
#50410 opened Feb 11, 2025 by tani
[Ray core] surface the node id/ip and other info (task name, etc.) in the stacktrace for a full object store core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability observability Issues related to the Ray Dashboard, Logging, Metrics, Tracing, and/or Profiling P1 Issue that should be fixed within a few weeks
#50408 opened Feb 11, 2025 by scottsun94
ProTip! Updated in the last three days: updated:>2025-02-11.