Andreas Reich

Now that pixi.toml recently broke forward compatibility, this would be particularly useful - we have users coming in with latest pixi and then not being able to use it because...

another motivation is size (see #6976): > When logging a lot of images, the data in rerun grows quickly. A lot of images are RGB heatmaps that stem from grayscale...

Yes absolutely. Even with AA disabled, we still have one (down from several) test where this is needed and there is [many reasons](https://github.com/rerun-io/rerun/blob/andreas/test-docs/CONTRIBUTING.md#why-does-ci--another-computer-produce-a-different-image) why we may run into problems that...

The problem with the [workaround](https://github.com/emilk/egui/issues/5683#issuecomment-2636292412) we're using right now is that whenever we react to a `egui_kittest::SnapshotError::Diff {` and discard its error as passing, the image has already been updated....

Our CMake file is generally not set up for cross compilation and it's not something we test on CI either. Contributions very much welcome!

Related to: * https://github.com/rerun-io/rerun/issues/7445

this got fixed in 0.25 using using the `abscissa` component, see https://rerun.io/docs/reference/types/archetypes/bar_chart

> A simple and ideal demo would be a gstreamer pipeline or a raw h264 video file publishing data to rerun to visualize the stream. I didn't have much success...

We got a maintained snippet and an example now for the new `VideoStream` archetype! * https://github.com/rerun-io/rerun/blob/f8a3c2408ba4bd5a4af8ac659e8f19f92c264ba7/docs/snippets/all/archetypes/video_stream_synthetic.py * https://github.com/rerun-io/rerun/tree/f8a3c2408ba4bd5a4af8ac659e8f19f92c264ba7/examples/python/camera_video_stream Any feedback would be welcome very much, otherwise we'll most likely ship...

To clarify: It's super laggy regardless but if you enable the experimental WebGPU support in Chrome Linux (it's still not stable there iirc, right?) then it does get a lot...