-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix domain coordinator API #9
Comments
Hi @dirk-thomas. This was part of some work I did when I was contracting for Apex.AI. I'm no longer working with them. I think @dejanpan would be the guy who can help you get this taken care of. He can probably assign someone from the QA team to make the requested updates. |
A note for future implementers - it's probably sufficient to make the domain coordinator a context object and use it in a |
The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes ros2#9
The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes ros2#9 Signed-off-by: Timo Röhling <timo.roehling@fkie.fraunhofer.de>
The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes ros2#9 Signed-off-by: Timo Röhling <timo.roehling@fkie.fraunhofer.de>
The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes ros2#9 Signed-off-by: Timo Röhling <timo.roehling@fkie.fraunhofer.de>
The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes ros2#9 Signed-off-by: Timo Röhling <timo.roehling@fkie.fraunhofer.de>
The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes ros2#9 Signed-off-by: Timo Röhling <timo.roehling@fkie.fraunhofer.de>
The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes ros2#9 Signed-off-by: Timo Röhling <timo.roehling@fkie.fraunhofer.de>
* Refactor domain_coordinator API to use a context manager The domain_coordinator refactored to expose a single context manager which returns a unique ROS_DOMAIN_ID that is valid until the context goes out of scope. The function has been deliberately renamed to force fatal errors if the call site was not updated to use a "with" context. Fixes #9 Signed-off-by: Timo Röhling <timo.roehling@fkie.fraunhofer.de>
Follow up of #3.
At the moment the function
get_coordinated_domain_id
returns an object wrapping a socket and mentions in the docblock that it relies on the garbage collector to destroy the socket when no references are hold anymore. Since in Python the garbage collector might run anytime (or never) this isn't a viable API.During the tests even a warning is printed that the sockets are never being closed: https://ci.ros2.org/view/All/job/test_ci_windows/196/pytest-warnings/
@pbaughman Since you create the original pull request implementing this API can you please look into this and revise the API in a follow up PR to make it explicit and deterministic?
The text was updated successfully, but these errors were encountered: