-
Notifications
You must be signed in to change notification settings - Fork 79
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
LoadComposableNodes action blocks previous actions #107
Labels
bug
Something isn't working
Comments
jacobperron
added a commit
that referenced
this issue
Jan 16, 2020
Fixes #107. Signed-off-by: Jacob Perron <jacob@openrobotics.org>
nuclearsandwich
pushed a commit
that referenced
this issue
Mar 13, 2020
Fixes #107. Before, the first call to _load_in_sequence was not asynchronous, unlike it's recursive calls. This change makes the first call asynchronous. Signed-off-by: Jacob Perron <jacob@openrobotics.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
In particular, it would be really convenient to be able to start a node container just before some actions to load components into it. Maybe not a bug, but certainly a big usability improvement.
Required Info:
Steps to reproduce issue
Launch the following launch file:
Expected behavior
A container node starts and the composition talker component is loaded.
Actual behavior
The container does not start and so the
LoadComposableNodes
Additional information
I understand that the
LoadComposableNodes
action is blocking until the service is available. But my intuition says that since the ComposableNodeContainer action appears first, it should be started before the loading action starts.After talking with @wjwwood, it sounds like we should update the implementation of
LoadComposableNodes
so it waits for the service in a separate thread so that it doesn't block the asyncio loop.The text was updated successfully, but these errors were encountered: