Excessive exceptions in stack trace due to deprecated behavior, ray 2.35+

Open
  • Is something wrong?
#57 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
observability

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.

Description

part: dependencies type: bug

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.
Dominant language
Python
Stars
64
Forks
8
Avg merge
14h 24m
Merged PRs (30d)
2

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Point72/raydar

All issues in Point72/raydar

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.