Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service requester starting before responder causes timeout when both are in the same process #468

Closed
azeey opened this issue Jan 11, 2024 · 0 comments · Fixed by #470
Closed
Assignees
Labels
bug Something isn't working

Comments

@azeey
Copy link
Contributor

azeey commented Jan 11, 2024

Environment

  • OS Version: Ubuntu 22.04
  • Source or binary build? source, 764a04b

Description

  • Expected behavior: When the node of a service requester is started before the node of a responder, the service request should succeed as long as the responder is started before the requester's timeout.
  • Actual behavior: Currently, if the requester and responder are in different processes, the expected behavior occurs, but if they are in the same process, the requester will always time out.

Steps to reproduce

  1. Checkout the flaky_service branch from https://github.com/azeey/gz-transport/
  2. Build examples/requester.cc and run it.

The example shows that if the responder is started with a 2s delay in a separate thread, the request fails.

@azeey azeey added the bug Something isn't working label Jan 11, 2024
@caguero caguero mentioned this issue Jan 18, 2024
8 tasks
caguero added a commit that referenced this issue Feb 2, 2024
* Support request/advertise within the same process.

Signed-off-by: Carlos Agüero <caguero@openrobotics.org>

---------

Signed-off-by: Carlos Agüero <caguero@openrobotics.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants