fix(protobuf): deserialize bytes fields as Uint8Array instead of Array

[42arch]

Description

In parseChannel.ts, protobufjs was configured with the option bytes: Array during deserialization. This converted all binary fields (e.g., data in foxglove.CompressedImage) into JavaScript arrays of numbers. This broke the instanceof Uint8Array validation checks in the Image Panel's message handlers, preventing image topics in protobuf-encoded MCAP files (like NuScenes) from rendering. Change the configuration option to bytes: Uint8Array to preserve raw binary buffers and allow correct rendering of protobuf-based images.

Motivation / related issue

As shown in the screenshots, if the image topic in the MCAP file uses Protobuf encoding, it will not be rendered in the ImagePanel. Other topics using ROS1 or CDR (ROS 2) encoding are not affected.

Type of change

• Bug fix (non-breaking change that fixes an issue)

Checklist

• npm run lint passes with no errors
• npm test passes (unit tests)
• npm run build and npm run build:lib succeed
• New behavior is covered by tests (or explain why tests aren't applicable)
• Documentation updated (README, API.md, EMBEDDING.md) if the public API changed
• Breaking change: all affected call sites updated and migration path described in PR description

API compatibility

N/A

Screenshots / recordings

Before:

After:

[joaner]

Thank you @42arch for the fix!

Switching protobufjs bytes deserialization to Uint8Array correctly restores Image Panel rendering for protobuf-encoded MCAP image topics. Great catch with a minimal, targeted change.