-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use canonical path for calls to ZarrService #57
Conversation
Unit test failures, investigating now |
Conflicting PR. Removed from build BIOFORMATS-push#535. See the console output for more details.
--conflicts |
Ah, @dgault, looks like we will need to start excluding or merging things. |
Conflicting PR. Removed from build BIOFORMATS-push#29. See the console output for more details.
|
The exception is gone, but for some reason the files are still not being detected. For /tmp/b.ome.zarr which is a symlink to /tmp/a.ome.zarr:
as opposed to
|
From a private message to David,
|
With the new commit:
and
👍 |
Conflicting PR. Removed from build BIOFORMATS-push#31. See the console output for more details.
--conflicts |
Conflicting PR. Removed from build BIOFORMATS-push#27. See the console output for more details.
--conflicts |
This PR is open for the purpose of testing the OMERO symlink issues.
Although we do not want to be using canonical paths within the reader, it seems that doing so when calling jzarr, does seem to resolve the issues and exceptions seen. I would expect a better long term solution would be to resolve this either at the JZarr level or within the ZarrService which call JZarr.