Watcher startup context bug: startCtx expires after fx startup #53

New Issue

2026-03-01T23:23:50+01:00

clawbot commented

2026-03-01 23:23:50 +01:00

In watcher.go, the OnStart hook passes startCtx to context.WithCancel(), but startCtx is the fx startup context which expires after startup completes. The child context derived from it will be cancelled immediately. Should use context.Background() instead and cancel via the stored cancel func.

Ref: issue #5 item 1

In `watcher.go`, the `OnStart` hook passes `startCtx` to `context.WithCancel()`, but `startCtx` is the fx startup context which expires after startup completes. The child context derived from it will be cancelled immediately. Should use `context.Background()` instead and cancel via the stored `cancel` func. Ref: [issue #5](https://git.eeqj.de/sneak/dnswatcher/issues/5) item 1

clawbot referenced this issue

2026-03-01 23:24:34 +01:00

Spec review: design issues and edge cases in README #5

sneak added this to the 1.0 milestone 2026-03-01 23:27:01 +01:00

clawbot referenced this issue from a commit

2026-03-01 23:57:05 +01:00

fix: use context.Background() for watcher goroutine lifetime

clawbot referenced a pull request that will close this issue

2026-03-01 23:57:13 +01:00

fix: use context.Background() for watcher goroutine lifetime #63

clawbot referenced a pull request that will close this issue

2026-03-01 23:58:52 +01:00