search

bcdev / zappend

Robustly creating and updating Zarr data cubes from smaller subsets
https://bcdev.github.io/zappend/
MIT License
40 stars 1 forks source link

Lock files are not created or removed #55

Closed TonioF closed 8 months ago

TonioF commented 9 months ago

I tried to run zappend (v 0.4.0) from the command line with 

zappend -t out/output.zarr in/*.zarr

Computation failed with message: 

Error: [Errno 2] No such file or directory: '.../out/output.zarr.lock'

After I created the .lock file myself, computation worked. After it finished successfully, I had to remove the file which was still there. My processing system is CentOS.

As I write this down, I notice that the lock file stated above is not correct, as it should be within the zarr folder, which it isn't.

TonioF commented 9 months ago

One more comment: The file name of my target zarr contained a .

Maybe that has something to do with it.

forman commented 9 months ago

@TonioF thanks, this is really strange, never seen this problem so far. Could you please try the same using the Python zappend() function, so we get a traceback. Btw, a traceback also when using the CLI would be good to have.

forman commented 9 months ago

traceback: #57

forman commented 8 months ago

The issue was a misleading error message. The root cause is that the target parent directory must exist, out in your case obviously did not.

Closed by #63