BUG: zero-length tensor contractions ignore requested output types
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start by reading the zero-contraction fast path in sparse.tensordot and the existing tests for tensor contractions. Add regression coverage for COO, GCXS and mixed dense inputs across the supported return_type values; the issue says a 32-case matrix reproduces the behavior. Done means output type, values, shape and dtype match the requested type and NumPy expectations.
Written by the indexing model from the issue text.
Description
Bug
The zero-contraction fast path in sparse.tensordot ignores return_type and does not preserve the normal default GCXS output selection.
Reproduced on main at d63255057744331b96626a1f1c24504b3a3783cd.
import numpy as np
import sparse
a = sparse.COO.from_numpy(np.empty((2, 0), dtype=np.float32))
b = sparse.COO.from_numpy(np.empty((0, 3), dtype=np.float32))
result = sparse.tensordot(a, b, axes=1, return_type=np.ndarray)
assert isinstance(result, np.ndarray) # fails: result is COO
Conversely, mixing a dense operand with a sparse one returns an ndarray even when return_type=COO or GCXS is explicitly requested. Two GCXS operands also return COO by default on this fast path, unlike non-empty contractions.
A fix and a 32-case regression matrix are ready. The matrix covers COO, GCXS and mixed dense inputs and all supported explicit output types; 19 cases fail before the production change. Numerical values, output shapes and dtype are compared with NumPy.
This is an AI-assisted bug investigation with locally executed reproductions and tests. No assignment is requested.
- Dominant language
- Python
- Stars
- 670
- Forks
- 167
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pydata/sparse
-
Bug: full einsum contractions upcast the dtype and count booleansPossibly taken @RaphaelFakhri claimed this 17 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
BUG: ufunc outer rejects Python scalar and sequence operandsPossibly taken @nawaaaaaAaar claimed this 29 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
Bug: slices with a negative step and a negative stop return wrong elementsPossibly taken @JoeyTan21 claimed this 19 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 75/100
pydata/sparse#1019 · 1 comment ·
Maintainers usually reply within 2 days
-
BUG: matmul fails with zero-length broadcast batch dimensionsPossibly taken @nawaaaaaAaar claimed this 29 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 40/100
Maintainers usually reply within 2 days
-
BUG: inferred COO reshape dimensions lose integer precisionPossibly taken @nawaaaaaAaar claimed this 29 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
abetlen/llama-cpp-python#2424 ·
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
jqueryscript/awesome-claude-code#1009 ·
-
tests
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day