You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run test_http_access.py in an appropriate virtual environment:
python test_http_access.pyZarr array available at url='http://localhost:3000/vizarr/data/zarr-files/20200812-CardiomyocyteDifferentiation14-Cycle1_mip.zarr/B/03/0/0'WITH CREDENTIALS:array_zarr=<zarr.core.Array (3, 1, 2160, 5120) uint16>WITHOUT CREDENTIALSTraceback (most recent call last): File "/home/tommaso/Fractal/http-zarr/open_remote_zarr_docker.py", line 24, in <module> array_zarr = zarr.open_array(store) File "/home/tommaso/Fractal/http-zarr/venv/lib/python3.10/site-packages/zarr/creation.py", line 649, in open_array init_array( File "/home/tommaso/Fractal/http-zarr/venv/lib/python3.10/site-packages/zarr/storage.py", line 455, in init_array _init_array_metadata( File "/home/tommaso/Fractal/http-zarr/venv/lib/python3.10/site-packages/zarr/storage.py", line 536, in _init_array_metadata shape = normalize_shape(shape) + dtype.shape File "/home/tommaso/Fractal/http-zarr/venv/lib/python3.10/site-packages/zarr/util.py", line 83, in normalize_shape raise TypeError("shape is None")TypeError: shape is None
The text was updated successfully, but these errors were encountered:
In case it's useful, it is easy to add this to some GitHub Action.
The easiest would be to replace docker run with docker run --detach, and then you can directly use data in localhost:3000/vizarr/data/zarr-files/. And/or you can customize the Dockerfile to use whatever example dataset you have (e.g. something local, so that you won't have to fetch data from Zenodo during each build time).
For the moment, I am using a public ome-zarr on github. But yeah, the tiny-http-server seems to be a better solution for the normal CIs (plus, I can also test authentication).
The docker CI might be a bit overkill for the current state of ngio, but at some point it would make so much sense to use it for larger integration runs (maybe weekly scheduled actions).
With @zonia3000, we prepared a testing environment for HTTP data access that requires BasicAuth (i.e. username and password) authentication.
Dockerfile
:build_and_run.sh
scriptbuild_and_run.sh
:At this point, you can access a file if you use the
myusername
/mypassword
credentials (as an example, try accessing http://localhost:3000/vizarr/data/zarr-files/20200812-CardiomyocyteDifferentiation14-Cycle1_mip.zarr/B/03/0/0/.zarray in the browser).Prepare the following
test_http_access.py
scripttest_http_access.py
in an appropriate virtual environment:The text was updated successfully, but these errors were encountered: