Files

T

osobhandClaude Opus 5.5 a6e90f3ee3 fix(format): apply the base address of files with a user block

A file may start with a user block (h5py userblock_size, h5jam), putting
the superblock at 512, 1024, ...; every address in the file is then
relative to the superblock. The signature search found it, but every
reader passed the whole file to the parsers, so addresses landed
userblock bytes early and the root group failed with
InvalidObjectHeaderVersion (twithub.h5, twithub513.h5,
h5clear_fsm_persist_user_*.h5).

Readers now view the file from the superblock on, taking the signature's
position as the base address as libhdf5 does: File (mmap, buffered,
from_bytes), MmapFile, LazyFile, AsyncHDF5File, the VOL and MPI VOL
readers, the HNSW loader and external VDS source files. File, MmapFile
and LazyFile gain user_block_size(). The new signature::split_user_block
returns the two parts, and Superblock::parse refuses a non-zero offset
(UserBlockNotStripped) so a format-level caller cannot silently apply
superblock-relative addresses to the whole file.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

2026-09-25 22:07:50 -05:00

src

fix(format): apply the base address of files with a user block

2026-09-25 22:07:50 -05:00

Cargo.toml

build: declare Rust 1.92 as the MSRV and check it in CI

2026-09-23 11:05:26 -05:00

README.md

docs: fix stale package names, counts, and CLI subcommands

2026-06-03 11:17:04 +00:00

README.md

clawhdf5-io

I/O abstraction layer for clawhdf5.

Features

Memory-mapped file access (mmap feature)
Async I/O via Tokio (async feature)
HSDS remote access (hsds feature)
Prefetching and sweep optimizations

Usage

use clawhdf5_io::MmapReader;

let reader = MmapReader::open("data.h5").unwrap();

License

MIT