ros-foxglove-bridge
ros-foxglove-bridge copied to clipboard
foxglove
Foxglove WebSocket Protocol bridge for ROS 1 and ROS 2
### Public-Facing Changes - Clients to the ROS 2 bridge can publish messages as JSON instead of `cdr`. JSON payloads will be re-serialized to `cdr` by the bridge before publishing...
**Description** Version: - foxglove studio: 1.87.0 - foxglove bridge 0.7.4 **Steps To Reproduce** Connection: Live connections to ROS2 humble with websockets 1- In foxglove studio open 3 Tabs: 2 with...
**Description** Foxglove studio can be reset by sending a new `serverInfo` message. The server currently does this only when the client connects, but we could also add a simple ROS...
**Description** Right now there is a lot of duplicated code. Should be deduped.
Revisit testing code that uses std::future / std::promise _Originally posted by @jtbandes in https://github.com/foxglove/ros-foxglove-bridge/pull/232#discussion_r1258690005_
Personally, my strategy with clang is usually to start with `-Weverything` and disable the annoying warnings. _Originally posted by @jtbandes in https://github.com/foxglove/ros-foxglove-bridge/pull/194#pullrequestreview-1335200816_
Would be great to get integration tests some day that can cover this functionality. _Originally posted by @jtbandes in https://github.com/foxglove/ros-foxglove-bridge/pull/182#pullrequestreview-1329298462_
Since this bridge makes use of the Foxglove WebSocket protocol, the generic C++ server implementation should live with the rest of the code at https://github.com/foxglove/ws-protocol. Unless there is a particular...
Is there a way we can add tests for these things? _Originally posted by @jtbandes in https://github.com/foxglove/ros-foxglove-bridge/issues/100#issuecomment-1334123733_
Taken from rosbridge: ``` # Publisher for number of connected clients # QoS profile with transient local durability (latched topic in ROS 1). client_count_qos_profile = QoSProfile( depth=10, durability=DurabilityPolicy.TRANSIENT_LOCAL, ) RosbridgeWebSocket.client_count_pub...