golang-context

Propagate Go context cancellation by passing the context as the first argument in function signatures and using r.Context in HTTP handlers to ensure deadlines and cancellation signals flow cleanly to databases and outbound API calls.

Your Go background work gets cancelled because it is tied to the request context. Use context.WithoutCancel to detach the asynchronous work so it survives past the request lifecycle without triggering premature cancellation.

The best way to pass request-scoped values in Golang is using context.WithValue with unexported key types for metadata like trace IDs, which keeps the data scoped to the request without polluting function parameters.

Fix context leaks in Go by calling the generated cancel function immediately after the context.WithTimeout or WithCancel operation, ensuring proper cleanup to avoid stuck work and leaked goroutines during code review.

You should not store a Go context inside a struct because it obscures lifecycle management and breaks propagation discipline; contexts should be passed explicitly to functions to maintain cancellation and deadline integrity.

Migrate legacy Go APIs by introducing context.TODO for incomplete migrations and gradually updating function signatures to accept context.Context as the first parameter, ensuring the codebase compiles during the transition.