parameter API does not allow to distinguish error cases
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
E.g. https://github.com/ros2/rclcpp/blob/249b7d80d8f677edcda05052f598de84f4c2181c/rclcpp/src/rclcpp/parameter_client.cpp#L246-L257 return an empty vector if something goes wrong which is also a valid response.
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
Start with rclcpp/src/rclcpp/parameter_client.cpp at lines 246-257 and read the surrounding parameter-client API. Determine how an empty vector is currently used for both failure and a valid response. Done means callers can distinguish those cases, with corresponding tests or documented verification added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, robotics
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100