Records/pypi/pymatting/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 1.1.15 FAIL

Where it reproduced

• executionContext=python · moduleSystem=standard · os=linux · runtime=python@3.12 ×5 2026-09-02 → 2026-09-03
• executionContext=python · os=linux · runtime=python@3.12 ×5 2026-09-02 → 2026-09-03
• os=windows · runtime=python@3.10 ×4 2026-08-25 → 2026-08-26

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• No release in this window recorded a passing observation at PROJECT_TEST.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• pymatting 1.1.15: lbdm_laplacian Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpymatting.lbdm_laplacian MIT-0 · 2026-09-02
• pymatting 1.1.15: estimate_foreground_cf Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpymatting.estimate_foreground_cfpython 3.12 MIT-0 · 2026-09-02
• pymatting 1.1.15: lkm_laplacian Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpymatting.lkm_laplacianpython 3.12 MIT-0 · 2026-09-02