Closed CodyCBakerPhD closed 4 months ago
From the traceback it looks like this fails when it tries to read the first element of the data set data = zarr_obj[0]
and it looks like the error occurs in numcodec
rather than Zarr
. What confuses me is the error ValueError: buffer source array is read-only
, which seems to indicate that blosc
wants write access even when reading from file. I'm wondering whether this may be an issue in Zarr
or numcodec
instead of hdmf_zarr
A couple of things to try:
a
instead of r
to see if that fixes the issue, i.e., change this line to with BACKEND_NWB_IO[backend](path=nwbfile_path, mode="a") as io:
. If that works, then I think this may be an issue in Zarr.data = zarr_obj[0]
from the dataset that causes the issue? If that works, another thing to try is to open with consolidated metadata (because hdmf_zarr uses consolidated metadata by default)@mavaylon1 can you take this from here.
@oruebel I can, but I probably won't take a look till earliest end of next week. Does that fit your timeline?
Possibly related: #195
This seems to have been resolved by my fix and release in #195
What happened?
Just encountered test failure in NeuroConv due to latest Zarr release on May 7
Full log: https://github.com/catalystneuro/neuroconv/actions/runs/9005172770/job/24739878400
Including test case below, show have most of what you need to reproduce
Wanted to check if this has anything to do with how the file is being read on hdmf-zarr side, or otherwise just let y'all be aware of the issue
Steps to Reproduce
Traceback
Operating System
Windows
Python Executable
Conda
Python Version
3.8
Package Versions
No response
Code of Conduct