[WASM] SChunk.__getitem__/get_slice raises RuntimeError on Pyodide 0.29.4 (works on 0.29.3 and 314.0.0)

Open
#664 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python, wasm

Research direction

Start with tests/test_open.py::test_load_schunk_returns_in_memory_copy and reproduce the failure under Pyodide 0.29.4, then inspect the schunk.py get_slice/getitem path and the blosc2_ext.pyx entry point named in the traceback. Check .github/workflows/cibuildwheels.yml and wasm.yml for the Pyodide version handling. Done means in-memory frame-loaded SChunk slicing works on 0.29.4 without regressing the passing 0.29.3 and 314.0.0 environments.

Written by the indexing model from the issue text.

Description

Summary

On the WASM/Pyodide build, slicing an in-memory SChunk that was loaded from
a frame fails with RuntimeError: Error while getting the slice — but only
under Pyodide 0.29.4
. The same code passes on Pyodide 0.29.3 (cp313) and
314.0.0 (cp314).

The wheel tag is pyemscripten_2025_0_wasm32 (ABI-level), so a wheel built/tested
against 0.29.3 still runs on a user's 0.29.4 runtime — meaning this is a genuine
runtime failure for 0.29.4 users, not just a CI artifact.

Reproducer

tests/test_open.py::test_load_schunk_returns_in_memory_copy:

urlpath = tmp_path / "schunk.b2frame"
data = np.arange(20, dtype=np.int32)
blosc2.SChunk(data=data, urlpath=urlpath, mode="w",
              cparams={"typesize": data.dtype.itemsize})
loaded = blosc2.load(urlpath)          # in-memory copy, urlpath is None
assert loaded[:] == data.tobytes()     # <-- RuntimeError here

Traceback

schunk.py:1114 getitem -> get_slice(item.start, item.stop)
schunk.py:1058 get_slice -> super().get_slice(start, stop, out)
blosc2_ext.pyx:2058 -> RuntimeError: Error while getting the slice

Environment matrix

│        Python / ABI         │ Pyodide │     Result      │
│ cp313 / pyemscripten_2025_0 │ 0.29.3  │ ✅ pass         │
│ cp313 / pyemscripten_2025_0 │ 0.29.4  │ ❌ RuntimeError │
│ cp314 / pyemscripten_2026_0 │ 314.0.0 │ ✅ pass         │

Current workaround

.github/workflows/cibuildwheels.yml pins CIBW_PYODIDE_VERSION: 0.29.3 for the
cp313 wasm job (cibuildwheel 4.1's default is 0.29.4). This keeps CI green and
matches the wheels wasm.yml already ships, but does not fix the runtime for
0.29.4 users.

Dominant language
Python
Stars
211
Forks
63
Avg merge
1d 7h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Blosc/python-blosc2

All issues in Blosc/python-blosc2

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.