exceptions raised in the server should be signaled to the client
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
This feature is available in ROS 1 and has proven to be very valuable. Otherwise every service would need to implement this basic kind of error handling itself.
Contributor guide
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
The issue does not name any rclcpp files, tests, or entry points. Start by reviewing how ROS 1 signals server-side service exceptions to clients and locating the corresponding service server and client paths in rclcpp. Done means the behavior is defined and implemented with coverage for server exceptions reaching the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100