Excessive exceptions in stack trace due to deprecated behavior, ray 2.35+
Open
Nobody has claimed this yet.
part: dependencies
type: bug
- Dominant language
- Python
- Stars
- 63
- Forks
- 8
- Avg merge
- 1h 57m
- Merged PRs (30d)
- 13
Description
running the demo yields:
ray.serve.exceptions.RayServeException: `DeploymentResponse` is not serializable. If you are passing the `DeploymentResponse` in a nested object (e.g. a list or dictionary) to a downstream deployment handle call, that is no longer supported. Please only pass `DeploymentResponse` objects as top level arguments.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the demo described in the issue under Ray 2.35+ and inspect the resulting stack trace. Trace the deprecated DeploymentResponse behavior and verify that the excessive exceptions no longer appear when the demo completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100