go

Fix goroutine leaks in Go production code by implementing structured concurrency with explicit lifecycle controls. This ensures goroutines terminate properly when their parent operations complete, preventing resource leaks and unexpected behavior.

Propagate context.Context through a Go service by passing it as the first parameter in function signatures. This pattern maintains cancellation signals and timeouts across the entire call chain, ensuring reliable context propagation in HTTP handlers and services.

Go error handling loses context when errors are returned unwrapped. Always wrap errors with contextual information using error wrapping patterns to propagate actionable diagnostics up the call chain for effective debugging.

Structure table-driven tests for Go HTTP handlers by defining test cases in slices with input arguments and expected outcomes, then iterating through them to execute robust error checking and validate handler behavior comprehensively.

Yes, use small, use-at-point interfaces to build testable Go project layouts. Defining interfaces where they are consumed rather than at package boundaries ensures components remain decoupled, mockable, and aligned with standard repository patterns.

Common Go production patterns causing issues include missing context propagation, unwrapped errors, unmanaged goroutine lifecycles, and poor project structure. Identifying and fixing these patterns prevents leaks and ensures clear, actionable error reporting.