fix(format): parse compound datatype versions 1 and 2 correctly

Browse Source

Compound datasets written with default libver bounds (datatype message
version 1, i.e. plain h5py.File(path, 'w')) could not be read: the v1 member
layout has 28 bytes of legacy array fields after the byte offset
(dimensionality 1, reserved 3, permutation 4, reserved 4, four sizes 16) and
the parser skipped 24, so every following member was read 4 bytes off. v2 was
also wrong: it keeps the 8-byte name padding and has no array fields.

Found by adding a default-libver axis to the h5py-generated-file tests (HDF5
2.0 raised the default low bound to 1.8, so "default" files are a distinct
format path from libver='latest'). Adds byte-level v1/v2 regression tests, a
truncation test, and fuzz corpus seeds for v1 compound and native complex.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

...

This commit is contained in:

osobh

2026-09-19 05:36:22 -07:00

co-authored by Claude Fable 5.1

parent a8ab9ca054

commit 926dc457e0

4 changed files with 137 additions and 22 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

crates/clawhdf5-format/fuzz/corpus/fuzz_datatype/seed_complex_f64_hdf5_2_0

BIN

Binary file not shown.

crates/clawhdf5-format/fuzz/corpus/fuzz_datatype/seed_compound_v1_default_libver

BIN

Binary file not shown.