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

Pub/sub across different nodes in same executor does not work #86

Closed
jacquelinekay opened this issue Aug 13, 2015 · 2 comments
Closed
Assignees

Comments

@jacquelinekay
Copy link
Contributor

Branch multiple_nodes in system_tests, package test_rclcpp, illustrates this bug:
https://github.com/ros2/system_tests/tree/multiple_nodes

Case 1 fails:
node1 and node2 are both added to one executor.
node1 publishes "foo", node2 subscribes to "foo"
node2 publishes "bar", node2 subscribes to "bar"
Both publishers publish 5 times.
0/5 messages are received for both subscribers.

Case 2 passes:
one node publishes "foo", "bar", subscribes to "foo" and "bar"
Both publishers publish 5 times.
5/5 messages are received for both subscribers.

Case 3 passes:
node1 and node2 both added to one executor.
node1 publishes "foo", subscribes to "foo"
node2 publishes "bar", subscribes to "bar"
Both publishers publish 5 times.
5/5 messages are received for both subscribers.

@jacquelinekay jacquelinekay self-assigned this Aug 13, 2015
@wjwwood
Copy link
Member

wjwwood commented Aug 13, 2015

Is this consistent across vendors?

@jacquelinekay
Copy link
Contributor Author

Actually, it looks like it's specific to Connext. I should probably move
this issue from rclcpp to rmw_connext, then.

On Thu, Aug 13, 2015 at 3:22 PM, William Woodall [email protected]
wrote:

Is this consistent across vendors?


Reply to this email directly or view it on GitHub
#86 (comment).

nnmm pushed a commit to ApexAI/rclcpp that referenced this issue Jul 9, 2022
nnmm pushed a commit to ApexAI/rclcpp that referenced this issue Jul 9, 2022
DensoADAS pushed a commit to DensoADAS/rclcpp that referenced this issue Aug 5, 2022
* enforce unique node names

* fix cppcheck
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants