Nicolas De LoofandClaude Fable 5 39193657eb fix(provider): deploy the relay outside the shared project mutex ...

runPlugin held the global mutex — there to guard concurrent writes to
project.Services — across ensureServiceRelay, whose Docker API work
(list, create, image pull, start, a 30s removal wait) forced every
concurrent provider to wait on the slowest one.

The mutex now covers only the shared-state work: env-var injection plus
the relay's network selection, which reads project.Services and must
not race with another provider's writes. The relay is deployed after
the lock is released, taking the pre-computed network keys — simply
unlocking around the call, as first suggested, would have traded the
serialization for a data race on the services map.

Co-Authored-By: Claude Fable 5 <[email protected]>
Signed-off-by: Nicolas De Loof <[email protected]>

2026-09-16 17:03:23 +02:00

..

api

feat(provider): publish-endpoint deploys a network relay for provider services

2026-09-16 17:03:23 +02:00

bridge

fix(bridge): confirm before wiping non-empty convert output dir

2026-09-03 14:38:41 +02:00

compose

fix(provider): deploy the relay outside the shared project mutex

2026-09-16 17:03:23 +02:00

dryrun

fix(dry-run): commit no longer creates a real image; the interception set becomes declarative

2026-09-16 13:44:21 +02:00

e2e

fix(provider): down removes the relay with the provider service

2026-09-16 17:03:23 +02:00

mocks

PRIVATE_PORT optional for docker compose port

2026-09-11 11:35:18 +02:00

remote

golangci-lint: enable perfsprint linter

2026-09-10 10:25:34 +02:00

utils

fix: make e2e tests pass reliably locally with Docker Desktop

2026-05-18 10:55:41 +02:00

watch

golangci-lint: enable perfsprint linter

2026-09-10 10:25:34 +02:00