-
Notifications
You must be signed in to change notification settings - Fork 237
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
Document that spin_once() should not be called from multiple threads #1079
Conversation
12e24cb
to
db9aae2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this depends on arguments, if user application calls rclpy::spin_once
with the same nodes and two different executor, this would be problem since we have a node in 2 wait sets. but we can create multiple threads to call SingleThreadedExecutor::snip_once:
for each node, that is usually what user would do.
Can you please suggest better wording for this PR?
This is what happened in my experience and it didn't work. I'd actually suggest to deprecate |
To be honest, i am not sure how to address this as documentation. How about adding
i believe we can have the same problem with
i understand, for user experience, probably thanks for iterating. |
@Mergifyio rebase |
❌ Unable to rebase: user
|
Signed-off-by: AndyZe <[email protected]>
Signed-off-by: Shane Loretz <[email protected]>
bf1aad9
to
63a2231
Compare
CI (repos file build: |
Fixes #1078