Benedikt Best

~~Does this also affect ilastik outside of tests?~~ Oh right, this has been status quo since 2020 🤦

I agree with the problem you mention - I'd be too worried that to circumvent the issue with spaces in the file names, people have hard-coded the specific file names...

Looks like the dependency conflict has cleared up, with python 3.11 we can have zarr v3 in the environment now. It doesn't support python 3.9 though, so will require some...

The target design for this (todo at some point) was to do nicknames like h5/n5, where we do `{container}-{internalpath}`. In this case, "2d_cells_apoptotic_1channel-s1". This would need to update when the...

Glad to hear you could figure it out 👀 I'm not really familiar with the implementation of `cutout_subregion` in headless, but from what you write I'm guessing it still operates...

Hi @Palak1725, the "Dataset Properties" dialog this refers to is the one that pops up when double-clicking a dataset in the Input Data step of any workflow.

Hi @Dev-Sudarshan, the address this issue, you need to know for which data types the current `0.1` is appropriate, and what would need to be different when it's inappropriate

Hi @ArnavBallinCode, sorry it took a while to get to this. The problem is a bit more complex unfortunately. Here's a test to illustrate what I think is the best...

Definitely the "meaningful error" route... the backend error would've been explicit, if the widget didn't already error out in the GUI: `raise ValueError(f"Multiple extensions unsupported as a single data source:...

Hi @Devesh-Yadav10, thanks for your suggestions. I think we can all come up with a variety of options for how to do this; the challenge really is to find a...