Field2d widget causes exception every frame about shuffleboard HOT 9 CLOSED

My guess is that the widget code doing the parsing doesn't match the Sendable implementation.
Can you send how the NT data looks (from any raw NT view)?

from shuffleboard.

There were several updates to the NT code in 2024.3.1. Can you confirm it still happens on that version or later (2024.3.2 was just released)?

from shuffleboard.

What is the type of Localized?
It should be a double[3].

Is it part of the Field2d publishing, or is it an entry you've published to that path?

from shuffleboard.

I don't have access to the robot, or a suitable testing environment right now, as I remembered this issue while doing a disk scan. Will update once I do.

from shuffleboard.

Can you please test a build from #798 and see that the issue doesn't reproduce and no other issues pop up?

from shuffleboard.

Incomplete data in map: {.name=Odom, .type=Field2d, .controllable=true, Robot=[D@35f5daf9, Localized=x: 1.4519350881997504, y: -31.02742566505306}

Where is this data coming from? That string for the "Localized" key is not a standard format that WPILib sends data in

from shuffleboard.

AFAIK we don't use NetworkTables at all in our robot code so anything there should be stuff published by WPILib.
I still haven't had a chance to test #798 yet, but tomorrow I should be able to test it.

from shuffleboard.

At minimum you're sending the Field2d object. What else are you sending? Note that the Shuffleboard and SmartDashboard APIs are NT wrappers...

Please go over your usage of the Shuffleboard API and check if you're publishing anything to the same path as the field.

Searching for "Localized" would also be a good guess to find what is being published and where.

from shuffleboard.

Across our entire SmartDashboard API calls, this line is the only one that includes the word "Localized", which seems suspiciously similar to the format of the data causing the exception. I don't think it's related to this issue though, as it publishes to a separate path, and the pose value in the exception is unlikely to come from this line, the robot would have to see an AprilTag from 30 meters away. We also don't publish anything to the same path of the field.

SmartDashboard.putString("Localized pose", "x: " + robot_actual_pose.getX() + ", y: " + robot_actual_pose.getY());

I'll look into our NT usage deeper once I'm able to work on the robot.

from shuffleboard.