Florian M

> Another way to handle this could be to simply choose the first occurring entry with a key when applying the metadata update in the fossildb. Meaning dropping the duplicate...

> border around the empty metadata placeholder in the dashboard is gone @MichaelBuessemeyer good catch, maybe you could fix that here directly?

> Yeah sure, do you think it looks visually fine this way? I mean the second image from my previous post I think it’s fine, yes. Mostly it’s consistent. We...

Looks like there are a couple of relevant bugs in this version. I’ll skip this release entirely, and release 24.11.1 instead in the coming days, starting from current master.

I’d say a delete route makes sense. Delete by hash. Only allowed for superusers. Use hard DELETE in postgres. This needs to cascade to all voxelytics tables. If the _voxelytics_workflowHash...

> It is possible to delete the workflow while it is running. Should this be disabled? This causes the workflow to fail, more or less as expected. It does not...

One thing that is similar would be layers_to_link concept in uploads, as offered by the backend. With that, you don’t have to reupload layers that are already present in wk,...

@philippotto A first rudimentary version seems to work: I can create an annotation on l4_sample, (note: volume buckets won’t load), take the annotation id and skeleton tracing id, and insert...

The next part of the frontend could be added now: The Restore Older Version flow. The version list view should no longer feature tabs per layer, but instead only one...

@MichaelBuessemeyer the next batch of frontend todos has arrived :innocent: I have not turned all of them into checkboxes in the description, feel free to do that if you prefer....