[BUG] Celery Background Callback Manager fails with Non-Key/Value-Backends
@datenzauberai ya está trabajando en esto.
Desde el 8/4/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Describe your context
This applies to background callbacks using the Celery Background Callback Manager. This should be reproducible using the latest version of dash as well.
dash 3.3.0
dash-ag-grid 33.3.3
dash-iconify 0.1.2
dash-mantine-components 2.5.1
dash-testing-stub 0.0.2
Describe the bug
Celery supports multiple backends that are not a BaseKeyValueStoreBackend:
CassandraBackendDatabaseBackendMongoBackendRPCBackend
However, Dash's CeleryManager assumes the backend to be a BaseKeyValueStoreBackend having the methods set and get.
Configuring any of the backends above will result in an error similar to AttributeError: 'DatabaseBackend' object has no attribute 'get' when triggering a background callback.
Backends that that implement BaseKeyValueStoreBackend might also fail, when the parameters passed to set and get do not comply with the backend's requirements (e.g. the FilesystemBackend expects a byte-like object for the key resulting in an error similar to TypeError: sequence item 1: expected a bytes-like object, str found, also see https://github.com/plotly/dash/issues/3116).
Expected behavior
The CeleryManager should either
- support all Celery backends by using
get_resultandstore_resultfromBaseBackendinstead ofgetandsetand using byte-like objects for keys or - make the restriction more explicit by additional documentation and erroring early on when the configured backend does not implement
BaseKeyValueStoreBackendor is otherwise not supported.
Especially the DatabaseBackend and FilesystemBackend would be accessible options without the need for additional infrastructure to execute background callbacks.
- Lenguaje dominante
- Python
- Estrellas
- 24.4k
- Forks
- 2.3k
- Merge medio
- 1 d 21 h
- PR fusionados (30 d)
- 19
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de plotly/dash
-
good first issue P3 size: 1 task
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement P2 size: 5
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
-
enhancement P3 size: 10+
-
P2 size: 1 task
-
enhancement P3 size: 1
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
Todos los issues de plotly/dash
Issues similares
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
canonical/paas-charm#368 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
tech debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
addition to tracking list Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
StevenBlack/hosts#3256 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
qualcomm/qai-appbuilder#275 ·