Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Scipy's spmatrix deprecation keeps the Upstream nightly red after #9351 — all 14 test_serialize_scipy_sparse cases fail

Abierto Apto para principiantes
  • ¿Algo no está bien?
#9,353 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
84/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
ci-cd, testing

Línea de trabajo

Comienza con los filtros de advertencias existentes de scipy en pyproject.toml y las 14 parametrizaciones de distributed/protocol/tests/test_scipy.py::test_serialize_scipy_sparse. Reproduce el fallo de advertencia como error en la configuración de pruebas nocturnas y, a continuación, verifica el manejo acotado de la obsolescencia de *_matrix a *_array. Se considera terminado cuando los 14 casos de serialización de scipy pasan sin ocultar advertencias no relacionadas.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

needs triage

Upstream stays red after #9351: behind the Bokeh hang it fixed there is a second, unrelated failure, dark since 2026-07-31.

What happens. scipy now warns on every *_matrix instantiation (scipy/sparse/_matrix.py: "…is being replaced by …_array. … The spmatrix classes will be removed no earlier than v2.2."). distributed's pytest config escalates warnings to errors (filterwarnings = ["error", …]), so all 14 parametrizations of distributed/protocol/tests/test_scipy.py::test_serialize_scipy_sparse fail:

E       DeprecationWarning: coo_matrix is being replaced by coo_array.

The first run to show it is the #9351 merge push itself (c88eb0b8, 2026-08-20): 14 failed, 2442 passed, 125 skipped in ubuntu-latest nightly test-ci not ci1 (job), the scipy cases being the only failures. The existing scipy entry in pyproject.toml's filterwarnings ("Please use dok_matrix from the scipy.sparse namespace…") matches the previous deprecation wave's message, not this one.

Why nobody could see it. Since 07-31 the Bokeh regression (#9350) hung this same job, so the nightly … not ci1 leg of every sampled scheduled run (07-31, 08-05, 08-10, 08-19) died at the 120-minute timeout as cancelled — no pytest summary, and upstream.yml uploads no artifacts. Scheduled runs have been red nightly since 07-31; last green was 07-30. #9351 unblocked the job; this failure is what was underneath, and the next scheduled run will surface it again.

Fix, your call: a scoped ignore beside the existing dok_matrix entry — something like '''ignore:\w+_matrix is being replaced by \w+_array''' (the matrix classes stay supported until scipy 2.2, and the test deliberately covers all seven) — or start migrating distributed/protocol/scipy.py and its test to sparse arrays now. I'd take the scoped ignore.

This report was researched and written by an AI agent (Claude Code) operated by @glaziermag. Every run link, job conclusion, and attribution above was re-verified against the GitHub API before filing.

Lenguaje dominante
Python
Estrellas
1.7k
Forks
778
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dask/distributed

Todos los issues de dask/distributed

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.