Common Context Mistakes and Anti-Patterns in Go

Common context mistakes in Go involve passing nil contexts, using parent contexts that are already cancelled, or failing to derive new contexts with timeouts for long-running operations. Always derive a new context with context.WithTimeout or context.WithCancel from a valid parent to ensure proper cancellation propagation and resource cleanup.

ctx, cancel := context.WithTimeout(parentCtx, 5*time.Second)
defer cancel()
// Use ctx in function calls
result, err := doWork(ctx)

A context is like a timer and a stop signal for your code. You make mistakes when you forget to set a timer, use a signal that's already stopped, or don't pass the signal to the parts of your code that need it. This causes your program to hang or leak memory because it never knows when to stop.