Donkie 6ade40517f backend: notify spools when their filament changes ...

Spool responses carry fields derived from the filament (remaining_length,
plus the initial_weight/price fall-backs). Editing a filament emitted only a
filament WS event, so subscribers to that filament's spools kept stale derived
values until each spool was next touched — visible in client_v2 as a length
inconsistent with the displayed density, but affecting every consumer.

filament.update now re-broadcasts the filament's spools (archived included)
as spool "updated" events after commit. Adds a WS integration test asserting
a density patch reaches /api/v1/spool with the new density and changed length.

Claude-Session: https://claude.ai/code/session_014Cwk5Yyze9yPvkYkUtMAP4

2026-07-21 10:58:09 +02:00

..

tests

backend: notify spools when their filament changes

2026-07-21 10:58:09 +02:00

__init__.py

Added script to easily run integration tests locally

2023-05-18 17:53:20 +02:00

docker-compose-cockroachdb.yml

Fixed timezone being returned incorrectly

2023-10-02 21:36:50 +02:00

docker-compose-mariadb.yml

Fixed timezone being returned incorrectly

2023-10-02 21:36:50 +02:00

docker-compose-postgres.yml

Make the integration test suite runnable under Podman

2026-07-06 12:16:17 +02:00

docker-compose-sqlite.yml

Fixed timezone being returned incorrectly

2023-10-02 21:36:50 +02:00

Dockerfile

Improved tests for add in integration tests

2023-05-28 21:40:17 +02:00

requirements.txt

backend: notify spools when their filament changes

2026-07-21 10:58:09 +02:00

run.py

Make the integration test suite runnable under Podman

2026-07-06 12:16:17 +02:00