Roman Shtylman

@james-rms I've updated the PR to use `utils.FormatTabe` and `humanBytes` as suggested. I've also made it more clear that the message size is `uncompressed` size by adding `(uncompressed)` to the...

@james-rms I've updated the PR to print a warning when the order is violated and print an error when the `--strict-message-order` flag is set.

+1 for not doing magic in `.send` for objects. Calling toString seems sensible over automagically returning JSON.

@filippobrizzi Thanks for proposing this change. While we have been silent here we have had some internal discussions around this. Unfortunately no internal champion has risen to own this and...

> what I do not understand is how do people use MCAP? It depends on your build system of choice. Here's one example with CMake: https://github.com/ros2/rosbag2/blob/rolling/mcap_vendor/CMakeLists.txt#L34 Where the build system...

Please split these up into separate PRs so we can consider each individually without holding up changes on the ones we want to spend more time on.

I suggest closing this issue. Right now there doesn't seem to be an urgency or workflow or need pushing this. I'm not sold on UUID semantics here and without the...

Maybe related PR: https://github.com/foxglove/mcap/pull/1322

cc @kscottz

Some of my thoughts and context on static/latching *tl;dr;* long-lived-static-data is always a mistake and trades off a slight convenience during "process restart"/"runtime" for hard-to-work-with data downstream when trying to...