compose/internal/sync
Guillaume Lours 467fa8ccc9 fix: share --parallel budget across down's ops and up's log-attach
down's outer ops dispatch bounded only how many ops ran concurrently,
separate from the semaphore already shared by image removal -- a
single network plus --rmi could spend up to 2x the configured
budget. Network and volume removal now share that same semaphore.

up's post-attach log streaming called ContainerInspect directly and
passed no limiter to doLogContainer, unlike `compose logs --follow`'s
equivalent path, so it never shared --parallel's budget either.

The plan executor also held a node's slot for its whole dependency
wait instead of just its own work, and internal/sync/tar.go's file
sync used a hardcoded cap of 16 instead of --parallel.

Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-01 16:02:14 +02:00
..
shared.go manage watch applied to mulitple services 2025-01-22 12:05:58 +01:00
tar.go fix: share --parallel budget across down's ops and up's log-attach 2026-10-01 16:02:14 +02:00
tar_test.go fix: share --parallel budget across down's ops and up's log-attach 2026-10-01 16:02:14 +02:00