maziggy d120a804ff fix(slicer): name the sidecar service in the update command (#2802) ...

The "update your sidecar image" advice told users to run a bare
`docker compose pull`. bambu-studio-api is declared with
`profiles: [bambu]`, and compose skips profile-gated services silently,
so the pull was a no-op for exactly the users the message was written
for -- and `restart: unless-stopped` kept the old container serving.
The reporter pulled, restarted, set MAX_MODEL_UPLOAD_MB and got the same
100 MB rejection, because the image never changed.

Name the service in both commands instead. Naming enables the profile
implicitly, for pull and up alike. `--profile bambu` would also work but
downloads the 220 MB Bambu image on an OrcaSlicer-only host and then
starts a sidecar the user never asked for.

Same correction in the sidecar README, the compose header and the
changelog entry, which all carried the bare form.

2026-08-11 08:35:23 +02:00

..

_fixtures

…

integration

Stop offering server-side slicing for STEP files

2026-08-10 13:09:24 +02:00

unit

fix(slicer): name the sidecar service in the update command (#2802)

2026-08-11 08:35:23 +02:00

__init__.py

…

conftest.py

implemented pr (worth fixing) feedback

2026-08-06 20:27:25 +02:00

pytest.ini

…