Data race when goroutines using context.Context outlive the http request about goji HOT 2 CLOSED

This is a bug in github.com/goji/context, not github.com/zenazn/goji. Unfortunately, that library is unmaintained (it was a proof-of-concept I wrote for someone), but I'd be happy to accept a patch.

As an aside, if you're using x/net/context you might want to have a look at the new version of Goji (https://github.com/goji/goji) which supports the package natively

from goji.

Yep, I've been following the new version and am planning on moving to that when it's ready.

The problem with github.com/goji/context is the 2 way binding, which makes it inherently request-scoped. I was using it as a wrapper for passing the content.Context object between middleware and on to the handler, but I can just store it directly in the Env object and avoid github.com/goji/context. I'll submit a README patch that adds this warning.

from goji.