Race condition introduced by PR #47 (which itself accidentally bundled Mistral autonomous Phase 3.2 work due to a working-directory race condition between Claude and Mistral — Q-038 to be added). Fix removes the informational log call from the cancel-handler goroutine; the flag-set is sufficient. go test -race ./pkg/config/... now passes. Full BDD green.
Race condition introduced by PR #47 (which itself accidentally bundled Mistral autonomous Phase 3.2 work due to a working-directory race condition between Claude and Mistral — Q-038 to be added). Fix removes the informational log call from the cancel-handler goroutine; the flag-set is sufficient. `go test -race ./pkg/config/...` now passes. Full BDD green.
The cancel-handler goroutine emitted a "watcher stopped" log AFTER
setting the watcherStopped flag. Because viper's internal watcher
goroutine (started by viper.WatchConfig) has no public Stop and can
outlive the context, this log call would race with subsequent
zerolog.SetGlobalLevel from the next test's LoadConfig → SetupLogging.
Symptom (under go test -race ./pkg/config/...):
WARNING: DATA RACE
Write at zerolog.SetGlobalLevel
Previous read by zerolog.(*Logger).disabled in log.Info(...)
Fix: drop the informational log. The flag is sufficient — the cancel
ack does not need to be observable. Test cleanups (defer cancel())
already serialize via the t.Cleanup teardown order.
Verified: go test -race ./pkg/config/... passes, full BDD suite green.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Race condition introduced by PR #47 (which itself accidentally bundled Mistral autonomous Phase 3.2 work due to a working-directory race condition between Claude and Mistral — Q-038 to be added). Fix removes the informational log call from the cancel-handler goroutine; the flag-set is sufficient.
go test -race ./pkg/config/...now passes. Full BDD green.