You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we don't use net/context, but we should. https://godoc.org/golang.org/x/net/context
Each piece of middleware, including the final handler, has no good context state. This is primarily irritating in the error handler, where we can't figure out what problems are because the value returned from panic() has no context other than the stack trace (i.e., no local variables, no URL, etc).
The text was updated successfully, but these errors were encountered:
Currently we don't use net/context, but we should. https://godoc.org/golang.org/x/net/context
Each piece of middleware, including the final handler, has no good context
state. This is primarily irritating in the error handler, where we can't
figure out what problems are because the value returned from panic() has
no context other than the stack trace (i.e., no local variables, no URL,
etc).
—
Reply to this email directly or view it on GitHub #73.
Currently we don't use
net/context
, but we should.https://godoc.org/golang.org/x/net/context
Each piece of middleware, including the final handler, has no good context state. This is primarily irritating in the error handler, where we can't figure out what problems are because the value returned from
panic()
has no context other than the stack trace (i.e., no local variables, no URL, etc).The text was updated successfully, but these errors were encountered: