Skip to content
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

[core][experimental] Support binding kwargs to DAG nodes in accelerated DAG #46274

Open
stephanie-wang opened this issue Jun 26, 2024 · 0 comments
Labels
accelerated-dag core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks UX The issue is not only about technical bugs

Comments

@stephanie-wang
Copy link
Contributor

Description

Allow binding DAG nodes to kwargs:

with InputNode() as inp:
  dag = a.foo.bind(x=inp)

Currently this does not work.

Use case

No response

@stephanie-wang stephanie-wang added enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component) accelerated-dag P1 Issue that should be fixed within a few weeks UX The issue is not only about technical bugs and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Jun 26, 2024
@rkooo567 rkooo567 added P0 Issues that should be fixed in short order and removed P1 Issue that should be fixed within a few weeks labels Aug 12, 2024
@anyscalesam anyscalesam added the core Issues that should be addressed in Ray Core label Aug 26, 2024
@stephanie-wang stephanie-wang added the good first issue Great starter issue for someone just starting to contribute to Ray label Sep 3, 2024
@jjyao jjyao added P1 Issue that should be fixed within a few weeks and removed good first issue Great starter issue for someone just starting to contribute to Ray P0 Issues that should be fixed in short order labels Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accelerated-dag core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks UX The issue is not only about technical bugs
Projects
None yet
Development

No branches or pull requests

4 participants