Skip to content

Parse error for numeric constant with leading zero #98

Open
@jtbandes

Description

@jtbandes

A user reported this in the Webviz Slack workspace.

Certain msg definitions (example kobuki_msgs/VersionInfo) have numeric constant with some leading zeros: uint64 SMOOTH_MOVE_START = 0000000000000001

ROS seems to handle this fine, but rosbag.js throws an error when trying to parse the constant, because JSON.parse throws. (@foxglove/rosmsg does handle it correctly, although I don't think we were aware of this bug/limitation when we wrote it.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions