mirror of
https://github.com/Dokploy/dokploy.git
synced 2026-09-14 11:06:15 +05:00
cee950b6c8
setupMonitoring's "is idempotent" test calls it twice back to back. Swarm keeps converging a freshly created service (scheduling tasks, resolving endpoints), which bumps Version.Index on its own shortly after creation. If that bump lands between the second call's inspect() and update(), Docker rejects it with "update out of sequence" even though nothing else touched the service. This never happens in production — setupMonitoring is only triggered by a UI button click or once during server setup, both far enough apart in wall-clock time for Swarm to settle. So the fix stays in the test: wait for two consecutive Version.Index reads to agree before making the second call. |
||
|---|---|---|
| .. | ||
| api | ||
| dokploy | ||
| monitoring | ||
| schedules | ||