Your problem is that commandcontext.run () waits for the command to finish before returning, so your cancelfunc.

Golang context background. Context.background() should be used only at the highest level of execution and only at once. Func testgetters(t *testing.t) { assert.false(t, isauthenticatedfromcontext(context.background())) _, err :=. Code should use context.todo when // it's unclear which context to use or it is not.

These values form a tree: The context module provides three functions that return a cancelfunc. Grasp basics about go context and avoid pitfalls.

Context is used to carry deadlines, cancelation signals, and values between concurrently running processes. Todo is recognized by static analysis tools that determine whether contexts are propagated correctly in a program. This can be done using the withcancel function in the context package, which returns a context object, and a function.

This function returns an empty context. The context package provides functions to derive new context values from existing ones. Applications in golang use contexts for controlling and managing very important aspects of reliable applications, such as cancellation and data.

Always use context.todo() when unclear about context or if it. On the second line of the main () function in the above snippet we’ve created a new context and a cancel function using withtimeout (): The golang standard library comes with a simple interface, context.context, which is a little harder to understand and use than the others.

This object provides a done signal channel that closes when. Ctx, cancel := context.withtimeout (context.background (), time.duration (time.millisecond*80)) defer cancel () req =. Yes, it's fine to use context.background () like this.