Go context misuse causes silent failures: two patterns developers should avoid

A technical deep-dive on DEV Community highlights two common but silent context-handling bugs in Go that compile cleanly yet cause real production issues. The first occurs when a goroutine launched inside an HTTP handler inherits the request context, which is cancelled as soon as the handler returns, causing background tasks like confirmation emails to silently fail. The second involves functions that accept a context parameter but internally use context.Background(), ignoring cancellation signals entirely and risking database connection pool exhaustion under load. Since Go 1.21, context.WithoutCancel() offers a clean fix for the first pattern by preserving request-scoped values while detaching from the parent's cancellation lifecycle. For both issues, the article recommends using the contextcheck linter and writing explicit cancellation propagation tests to catch regressions early.