forked from ray-project/ray
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[serve] Resolve
FunctionNode
with no arguments to RayServeHandle
,…
… not `RayServeDAGHandle` (ray-project#37261) Currently function deployments are resolved to `RayServeDAGHandle`s even if they are not used as part of the deployment graph API (with an `InputNode`). This leads to some unexpected behaviors such as `.options()` not working properly and input arguments not being propagated. This PR fixes the issue by replacing the function node with a regular `RayServeHandle` when there are zero bound arguments (which is always the case when not using the deployment graph API). I've also added a test to prevent us regressing on the handle typing.
- Loading branch information
Showing
4 changed files
with
88 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters