search

rerun-io / rerun

Visualize streams of multimodal data. Fast, easy to use, and simple to integrate. Built in Rust using egui.
https://rerun.io/
Apache License 2.0
5.66k stars 255 forks source link

GitHub Action/bot to create Rerun links for attached/linked RRD/files #4223

Open abey79 opened 7 months ago

abey79 commented 7 months ago

What if you could attach a .RRD (zipped, because GH doesn't allow otherwise) to a PR and automatically have a link to a PR-built app.rerun.io pointing at said .RRD?

What if users could simply drop a .RRD in their issue and an app.rerun.io a link would automatically show up, using the Rerun version stated in said issue?

. . .

What if users anywhere on [GitHub|Discord|Twitter|Mastodon|...] could link/attach any file that's supported by Rerun (natively and/or via an extension) and order a bot to "Open it in Rerun"?

rasmusgo commented 7 months ago

I was able to load an .rrd file uploaded to github by fiddling with the url a bit: https://app.rerun.io/?url=https://raw.githubusercontent.com/rasmusgo/morten-code/master/data.rrd. The fiddling was to manually follow the redirect and use raw.githubusercontent.com instead of github.com.

EDIT: I just realized you are trying to do something slightly different.

abey79 commented 7 months ago

Yeah there are two parts for this: 1) ingest what GitHub accept hosting 2) have a per-PR app.rerun.io build.

As for (1), how did you manage to upload a RRD? GitHub usually refuse anything that's not known extension (including .RRD), thus the idea of supporting .rrd.zip.

rasmusgo commented 6 months ago

I committed the RRD from my local machine manually and pushed.

emilk commented 2 months ago

One solution to this is for users to .zip the .rrd, attach it to a GH issue and have our web viewer read it. See: