via @jtbandes:

I should be able to publish a geometry_msgs/Twist to control turtlesim, even though there are no publishers for this topic yet.

This might mean we need to ship common datatype definitions with the app, if the md5sum needs to be correct.

rostopic pub does this by looking up the datatype definition on disk.

via @jhurliman:

We need to handle the XMLRPC calls coming in from rosmaster in addition to the TCP disconnect handling

From Jack Ma in Slack (via @jtbandes):

Apparently Webviz defaults to using 10000 (or 10 m), so everything just looks really black and quite basically unusable beyond those.

via @jtbandes:

• #1335
• #670
• #1365
• #1288
• #1005
• #1386
• #1337
• #1408
• #1409

Is there any way to publish the pose msg by click the point in 3D panel, just like the "2D Pose Estimate" button in rviz

via @jtbandes:

Node Playground lets you publish custom datatypes, but the datatype name that's exposed to the rest of the app is autogenerated. This means the message can't be used for other panels that are looking for specific datatypes.

We should consider allowing users to import custom data types for use in Node Playground that aren't part of the common ROS packages, but also aren't in their bag / data source.

(It would also be good to provide built-in definitions for the common ROS datatypes: #1261)

Sample bag: https://storage.googleapis.com/cartographer-public-data/bags/backpack_3d/with_intensities/b3-2016-04-05-14-14-00.bag

Repro by turning on horizontal_laser_3d topic and coloring by intensity.

This bag also has issues coloring /scan_cloud_aggregated by z, although x and y work:
https://storage.googleapis.com/cartographer-public-data/bags/taurob_tracker/taurob_tracker_simulation.bag

via @jtbandes

via @jtbandes:

In a Tab panel, it seems like currently the only way to get a new tab is to click the + button, then add a panel. It would be nice if you can simply drag an existing panel onto the new tab button to create a new tab with that panel.

Hi,

1. Love foxglove, it is awesome!
2. im having issues when connecting to my robot via websocket. when i connect and all of the nodes load foxglove shows an error:
   Expected 1 top level type definition for 'BaseRecoverResult' but found 2

BaseRecoveryResult.msg is made up of a bool field and a string field. this msg is used in a result topic of an action server.

here is a screen snap:

anyone know whats up?

via @jhurliman:

Ros1Player dynamically updates datatypes when connection headers are received from publishers, but Node Playground doesn't support dynamic updates of datatypes. This leads to nodes not compiling because the datatype TS definitions ("rosLib") are empty.

Start the ros1-turtlesim-test container, connect with FGS, and attempt to compile the following script in Node Playground:

import { Input, Messages } from "ros";

type GlobalVariables = { id: number };

export const inputs = ["/turtle1/color_sensor"];
export const output = "/webviz_node/color_sensor";

// Populate 'Input' with a parameter to properly type your inputs, e.g. 'Input<"/your_input_topic">'
const publisher = (
  message: Input<"/turtle1/color_sensor">,
  globalVars: GlobalVariables
): Messages.turtlesim__Color => {
  return { ...message };
};

export default publisher;

It fails with:

Cannot use namespace 'Input' as a type.(2709)
Namespace '"ros"' has no exported member 'turtlesim__Color'.(2694)

The error happens when you don't have an input source loaded. Maybe in that case we should produce a different more explicit error.

Once you connect an input source the input error goes away. Other errors might also go away depending on what messages your input source has.

via @jhurliman:

Editable table view of all TF values and the ability to add/delete/rename rows. This will need a clear button as well to reset back to TFs sourced from the player only.

via @jhurliman:

Once a matching rootTf is seen we could automatically switch to it.

via @jtbandes:

Sometimes you're zoomed too far in/out/etc. We should consider doing some rough bounding box calculations and show a little indicator pointing to where the markers are offscreen if nothing is visible.

To reproduce (in v0.6.0) just add Node Playground panel:

Placeholder ticket to discuss if ROS 2 websocket connections are interesting to anyone.

In theory we could allow connections over websocket (similar to what we support with rosbridge in ROS 1) using https://github.com/RobotWebTools/ros2-web-bridge.

However, we have also discussed a native-connection-over-ssh option which might be more useful than websocket connections. We're open to feedback.

See also:

• #715 (ROS 2 native connections)
• #717 (ROS 2 bag support)
• RobotWebTools/ros2-web-bridge#174
• RobotWebTools/rosbridge_suite#345

via @jtbandes:

cruise-automation/webviz#438

Info and repro steps for the original bug that required this workaround:

cruise-automation/webviz#24

via @jhurliman:

via @jtbandes:

I thought this used to be collapsible but it doesn't appear to be. The list of TFs can get very long, which pushes the actual viz topics lower and makes for a confusing experience. I guess it is collapsible in some cases — not sure why it wasn't in this case.

Overview

The 3D panel docs include this section on drawing polygons:

Of the functionality described above, only 1) drawing a polygon, 2) selecting a polygon, and 3) bisecting a polygon edge seem to be working. Selecting a point within the polygon, moving / resizing / deleting a polygon, deleting a point in the polygon, etc. are not working, at least not as described by the included documentation.

Steps to repro

• Open Foxglove Studio with demo bag: https://storage.googleapis.com/foxglove-public-assets/demo.bag
• Open 3D panel and click on pencil icon
• Hold Ctrl + click around on canvas to create a polygon
• All other interactions (selecting point, moving point, etc.) do not work as expected

Currently it doesn't load data until after you start playing the bag. Ideally it should display all the available data from the bag similar to plot panel.

• Connect to Websocket bridge
• Open a new Publish panel
• Whole app crashes irreparably

via @jtbandes

https://developer.microsoft.com/en-us/fluentui#/controls/web/list

Also does virtualized rendering. One less thing to keep updated.

When scrubbing, we should intelligently find the right message to display for topics which are published infrequently.

• Experimental play w/ support for .bag files
• #3027
• #3028
• #2899
• #1962
• #3361

References:

• cruise-automation/webviz#314
• ZebraDevs/webviz@ab301ca

cc @cjds

via Clement in Slack:

Another nice feature would be to be able to co-plot timed non-float values inside the plot pannel. Right now if you input a string submessage to plot. It does nothing. The state transition pannel is nice but it could be folded in the normal plot panel. Lets say you have a string message or state. You display a straight vertical line at the time of transition inside the plot.

Most messages have either a header stamp or receive time which would allow for arbitrary string fields to be plotted with vertical annotation/reference lines (we already have the annotation plugin).

Since v0.5 the app window is black and completely unresponsive (not even draggable) for 6-7 seconds).

@defunctzombie thinks it is due to loading all the panel code up front now.

Currently we just pretend they are a bag and show the spinner like we are waiting for them to come online or something.

We can start with something basic like this (what google docs gives you when you drop an unsupported file type):

It seems that I can't connect to a web socket source either (v0.3) . . .

I tested with webviz, and it seems to work fine, but foxglove gets stuck connecting.

Some more information:
OS: Ubuntu 20.04
ROS: Noetic
Foxglove: deb from the site
Webviz: docker (works when connecting to the ws server running locally and in a docker container)

dev console:

Stuck connecting when trying to open a connection to ROS on localhost (v0.3).

Placeholder ticket to discuss native ROS2 connections.

See also:

• #716 (ROS 2 websocket connections)
• #717 (ROS 2 bag support)

via @jhurliman:

Holding ~ brings up the secret UI for managing panels, but if you hold Ctrl+~ the secret UI still appears but none of the buttons are clickable and dragging no longer works. We should either disable the menu from appearing with this combo or allow the buttons to work.

For some reason it works fine when holding Cmd+~ or Option+~.

via @jhurliman:

This library has no test coverage right now and is susceptible to regressions that only show up when you try to use the ROS1 connector in FGS. Since this library is intrinsically tied to Electron implementation details, for full coverage we need an integration test that compiles a small electron app, runs it, and confirms socket and server creation and communication works as expected.

via @jhurliman:

You can see this in the raw message view for the demo bag, any large Uint8Array field is only fully viewable by logging to the dev console which we hide.

Saving to a binary file would be a sensible alternative.

Hello,
I installed foxglove v0.2.0 in a docker container.
After installation of foxglove, I'm unable to use roslaunch or rosrun on every package.
Verified with a new container. Deinstallation of foxglove-studio doesn't resolve the problem.
Foxglove-studio seems to work correctly on the same computer directly outside the container.

$ rosrun turtlesim turtlesim_node
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-student'
[ INFO] [1616618619.246782155]: Starting turtlesim with node name /turtlesim
[ INFO] [1616618619.251715865]: Spawning turtle [turtle1] at x=[5.544445], y=[5.544445], theta=[0.000000]
dbus[6192]: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)

System: Windows 10
Describe: After launch program, all panels disappear after a flash

via @jtbandes:

I can consistently repro this in the storybook scenario I newly added in #410.

This bug also exists in upstream webviz when tested with the same layout.

via @jhurliman:

It's currently possible to publish messages using the Publish panel when using rosbridge connections.

We should enable this when using ROS1 native connections.

We should support loading ROS 2 bags.

It seems that will be much more difficult than loading ROS 1 bags, since ROS 2 bags are not a self contained file, and the output folder can contain many different formats (sqlite is the default driver).

See also:

• #715 (ROS 2 native connections)
• #716 (ROS 2 websocket connections)

To reproduce this, try to load a bag that is not a valid rosbag file. The RandomAccessPlayer has a generic catch for any player errors that calls this._setError("Error initializing player", error, "app"); which reports this user error (opening a bad file) as an application error to Sentry. We need to surface this as a user error somehow.

via @jhurliman

via @jtbandes:

Rather than {config: {foo}, saveConfig} = props, panel authors should use something like [foo, saveFoo] = usePanelConfig("foo").

Since #622, one of these two functions is unused. If there are any differences we should merge them.

When I tried to publish a message which type is PoseWithCovarianceStamped, I counted this error described in title.

This is my detailed msg

{
"header": {
"seq": 10,
"stamp": {
"sec": 0,
"nsec": 10
},
"frame_id": "base_link"
},
"pose": {
"pose": {
"position": {
"x": 45,
"y": 0,
"z": 0
},
"orientation": {
"x": 0,
"y": 0,
"z": 0,
"w": 1
}
},
"covariance": [
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
]
}
}

What can I do to fix it?

via @jtbandes @jhurliman:

• Zooming with scroll wheel / trackpad pinch feels too slow
• Zoom percentage / menu looks strange – the percentage itself may not be that useful, and these menu items could probably be buttons instead for better UX
• Easy to get in a weird state where the image doesn't stay aligned as you resize the panel
• Max zoom of 150% is too small. It should be 200%

Trying to read a duration field from a message fails. This affects the Marker datatype. Broken in #622

From @jackma:

Render line breaks (or other simple formatting things) in the text field of 3D/2D viewer’s “Selected object” pop-out

via @defunctzombie:

Log panel current displays timestamps in unix time - we should have a setting to display the time in human readable format and follow the app's timezone settings