Closed caguero closed 3 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 87.67%. Comparing base (
eac2e69
) to head (687edcc
). Report is 3 commits behind head on gz-transport13.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Would it be possible to detect that the response type is Empty
instead of relying on the timeout to decide that the request is one way? I like the idea of making some of the arguments optional (see https://github.com/gazebosim/gz-transport/issues/475, https://github.com/gazebosim/gz-transport/issues/474, https://github.com/gazebosim/gz-transport/issues/473), but there is a lot of existing documentation that uses the --reptype gz.msgs.Empty
and --timeout
arguments. It would be nice if those commands didn't timeout as well.
26d669b
Sounds good to me. Then, now both:
gz service -s /oneway --reqtype gz.msgs.StringMsg --reptype gz.msgs.Empty --req 'data: "Hello"' --timeout 10
and
gz service -s /oneway --reqtype gz.msgs.StringMsg --req 'data: "Hello"'
shoudn't generate timeouts.
@j-rivero , do you know why the same job (Ubuntu CI / Ubuntu Jammy CI) can pass and fail at the same time? It seems that GZ_PATH
and g_gzVersion
is undefined.
There have been some changes in https://github.com/gazebosim/gz-transport/pull/481 that affect this PR. I suggest merging from gz-transport13
.
Good to go again!
🦟 Bug fix
Partially fixes #97
Summary
This patch makes it possible to request a one-way service request from the command line. Before, it was possible passing
--reptype gz.msgs.Empty
but always getting the messageService call timed out
as an output (because the service callback wasn't answering anything, which was expected).How to test it?
You can compile the examples, and then:
Launch the one-way responser:
Request the service using the two-way request and verify that you don't get the timeout:
Use the new one-way request and verify that you don't get the timeout message:
Note that both requests should reach the responser:
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.