77f33c2864
waitForStopped removed the run-file and then additionally waited for the daemon process to fully exit, erroring with "removed run-file but did not exit within 10s" if it lingered past the stop timeout. The run-file is the daemon's own liveness marker: once it is gone the daemon has committed to stopping. When no desktop client is connected the daemon can drain its background workers slower than the stop timeout, which made ao stop spuriously report failure (the TestE2E_Lifecycle failure in #2214). Treat run-file removal as stopped: keep polling for full process exit as a best effort (so Windows releases inherited handles before callers clean the data dir) but no longer error when that grace elapses. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| cmd | ||
| internal | ||
| .golangci.yml | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| sqlc.yaml | ||