Messages (and svcs and action goals) larger than a certain size seem to 'disappear'
@Acuadros95 is already working on this.
Since May 24, 2022.
Assessment
This issue has not been assessed yet.
Description
Describe the bug
Agents do not appear to forward messages coming in from the "ROS 2 side" that are larger than a certain size.
Increasing the verboseness of the Agent, DDS messages with len: 67776 for instance just disappear. There are no warnings or errors printed by the Agent, and the Client doesn't appear to receive anything, nor does it notify the Agent of any error.
For reference, this was also discussed in https://github.com/micro-ROS/rmw_microxrcedds/issues/258.
To Reproduce
Steps to reproduce the behaviour:
Not exactly steps, but at a high level:
- implement a Client capable of subscribing to a message with a variable sized payload
- create a
rclcpporrclpypublisher which publishes instances of this message - gradually increase size of the payload from something small to 'something large'
- notice how at a certain point, the Client no longer receives any messages
Alternatively: create a server service and client, or an action server and client, which exchange the described message (as one of the fields fi).
Service invocations and action goal submissions will silently start to fail for messages "too large".
Expected behaviour
Ideally: messages of all sizes (even large ones) get forwarded successfully.
Realistically (as unlimited memory doesn't exist): the Agent prints a warning or error, clearly showing it's impossible to forward a message.
If possible: in case of svcs and actions: notify the client the invocation failed -- due to RMW-level failures (so not the invocation itself, but the request didn't even arrive at the server).
System information (please complete the following information):
- OS: observed under Ubuntu
20.04, but same happens on other OS - ROS 2 Foxy, Galactic and Rolling
- Version: using the "most recent" Docker image (
microros/micro-ros-agent/5e93b1fa5608)
- Dominant language
- C++
- Stars
- 201
- Forks
- 111
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 10
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.
More from micro-ROS/micro-ROS-Agent
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
micro-ROS/micro-ROS-Agent#270 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
micro-ROS/micro-ROS-Agent#269 ·
-
Release to apt Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
micro-ROS/micro-ROS-Agent#267 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
micro-ROS/micro-ROS-Agent#266 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
micro-ROS/micro-ROS-Agent#265 · 1 comment ·
All issues in micro-ROS/micro-ROS-Agent
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mlcommons/mobile_app_open#1182 ·
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-cli#6547 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·