Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

Support CBOR in foxglove studio visualizer #330

Closed
therishidesai opened this issue Dec 6, 2022 · 2 comments
Closed

Support CBOR in foxglove studio visualizer #330

therishidesai opened this issue Dec 6, 2022 · 2 comments
Labels
feature A new feature or idea

Comments

@therishidesai
Copy link

I want to use CBOR as the serialization/deserialization method but when I use the "cbor" message encoding type in my MCAP file the foxglove studio visualizer errors with the following:

Error: Unsupported encoding cbor
    at parseChannel (https://studio.foxglove.dev/1023.b8837902683ffb518450.js:1:7731)
    at McapIndexedIterableSource.initialize (https://studio.foxglove.dev/4766.761276315d65092c2625.js:1:1915)
    at McapIterableSource.initialize (https://studio.foxglove.dev/4766.761276315d65092c2625.js:1:11413)
    at async WorkerIterableSourceWorker.initialize (https://studio.foxglove.dev/4126.a9f9b288f40cab96776f.js:1:20965)
@therishidesai therishidesai added the feature A new feature or idea label Dec 6, 2022
@therishidesai therishidesai changed the title Support CBOR foxglove studio visualizer Support CBOR in foxglove studio visualizer Dec 6, 2022
@therishidesai therishidesai mentioned this issue Dec 16, 2022
Closed
@jtbandes
Copy link
Member

jtbandes commented Dec 6, 2022

Also filed foxglove/mcap#763

@jtbandes
Copy link
Member

See also: json-schema-org/json-schema-spec#6

@amacneil amacneil transferred this issue from another repository Dec 16, 2022
@foxglove foxglove locked and limited conversation to collaborators Dec 16, 2022
@amacneil amacneil converted this issue into discussion #405 Dec 16, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
feature A new feature or idea
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jtbandes @therishidesai