4 Commits

Include renames

Author	SHA1	Message	Date
osobhandClaude Opus 5.5	e4ba09946f	HDF5 2.0 native complex as a first-class type on read; Python libver= ... - Datatype::parse returns Datatype::Complex for class 11 (also inside compounds, arrays and VL types) instead of the {r, i} compound view. - Facade: DType::Complex(Box<DType>); read_complex_f32/f64 accept it. - h5rs dump/ls/diff print native complex as h5dump/h5ls/h5diff 2.2.0 do (checked against a fixture written by h5py 3.16 / libhdf5 2.0.0); dump --json keeps the {r, i} compound (hdf5-json has no complex class). - clawhdf5-wasm reads native complex datasets as [re, im] pairs. - Python: clawhdf5.File(path, 'w', libver=...) with h5py's values, mapped to FileBuilder::libver_bounds; 'v108' output opens in HDF5 1.8.23. - Docs: known-issues entry moved to Fixed (history), CHANGELOG, READMEs. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-09-29 20:47:33 -05:00
osobhandClaude Opus 5.5	581c6ddef8	wasm-viewer tests: the cross-origin path without exposed headers ... serve.py always exposed Content-Range and ETag, and Node has no CORS, so openUrl's documented cross-origin path (length from a HEAD request, answers checked by body length alone, no validator) was never run. - serve.py /noexpose/ serves ranges without Content-Range, ETag, Last-Modified or Accept-Ranges (what a page sees of a server that does not expose them); /unexposed/ sends them but exposes none, for a real browser. HEAD requests are counted (0 bytes). - test.mjs: every fixture check through /noexpose/ at 1 MiB and 512-byte blocks (one HEAD each, requests and bytes as the server counted them), concurrent reads with cacheSize 0, a short answer still caught, and a server without a HEAD length a clear error. - browser.sh: the page on 127.0.0.1 opens the file from localhost, once with Content-Range exposed and once through /unexposed/, where the server's log must show the HEAD. Checked by breaking the HEAD length in remote.js: the new checks fail. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-09-27 07:51:30 -05:00
osobhandClaude Opus 5.5	b8c85f7627	wasm-viewer: open by URL, lazily, with a request counter ... The page gets a URL box; ?file=<url> now opens with openUrl instead of downloading the file, and the header shows the requests made and bytes fetched so far ("5 requests, 5 MiB of 191 MiB fetched (2.6%)"). Every file call is awaited, so local files (open) and remote ones share the code; a selection that finishes after another was made is not shown. browser.sh serves the page and fixtures with test/serve.py (no symlinks into the repository any more) and also checks a server without range support and, on the 200 MB file, that a small dataset and a window of the big one render with a single-digit percentage fetched. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-09-27 06:44:51 -05:00
osobhandClaude Opus 5.5	1abd93e0f8	feat(wasm): examples/wasm-viewer, an HDF5/NetCDF-4 viewer page ... Drop a file (or pass ?file=<url>&path=<object>), browse the tree lazily, see a dataset's type, shape, max shape and attributes, and page through its values as 50x12 hyperslab windows (leading dims of 3-D+ data held at chosen indices). build.sh produces pkg/ (not committed) with wasm-bindgen --target web and checks the CLI matches the crate version. test/run.sh builds it and runs test.mjs under Node against the h5py/ netCDF4 fixture (250 checks: every dataset whole and as a strided hyperslab, listings, attributes, error paths, the page's DOM-free helpers), then browser.sh renders the page in headless Chromium for eight objects and checks the DOM. The fixture gains LZ4 (read) and Zstd (refused: links C) datasets and a compound attribute (value null plus its type). ci-test.sh runs it when node and wasm-bindgen exist; the CI container has neither, so CI relies on the native h5py_interop test. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-09-26 00:05:34 -05:00