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

Subscriptions not working on ROS2 rolling #120

Closed
achim-k opened this issue Dec 16, 2022 · 3 comments · Fixed by #122
Closed

Subscriptions not working on ROS2 rolling #120

achim-k opened this issue Dec 16, 2022 · 3 comments · Fixed by #122
Assignees
Labels
bug Something isn't working

Comments

@achim-k
Copy link
Collaborator

achim-k commented Dec 16, 2022

Description

  • Version: latest
  • Platform: ROS2 rolling / ubuntu jammy (provided docker image)

Steps To Reproduce

  1. Run the bridge e.g. with docker run --pull --rm -it --name foxbridge --net=host ghcr.io/foxglove/rolling-ros2-bridge
  2. Publish a periodic topic e.g. docker exec -it foxbridge bash -c "source /opt/ros/rolling/setup.bash && ros2 topic pub /foo std_msgs/String data:\ 'hello'"
  3. Connect a client and observe that subscriptions are not working

Expected Behavior
Client should receive messages of subscribed channels

@achim-k achim-k added the bug Something isn't working label Dec 16, 2022
@defunctzombie
Copy link
Contributor

https://linear.app/foxglove/issue/FG-1034/subscriptions-not-working-on-ros2-rolling-[foxgloveros-foxglove-bridge

Don't know why the bot did not comment on this.

@achim-k
Copy link
Collaborator Author

achim-k commented Dec 16, 2022

Observation: Making a graph change by e.g. publishing on a random topic (ros2 topic pub /asdf std_msgs/String data:\ "meh") triggers the bridge to send messages to the client 🤔

@achim-k
Copy link
Collaborator Author

achim-k commented Dec 16, 2022

Underlying rclcpp issue: ros2/rclcpp#2067

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging a pull request may close this issue.

2 participants