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
I'm not entirely sure what information you'd need to help diagnose this. As far as I can tell the panicking stacktrace doesn't go through any of my code, and I'm not (intentionally) sharing the context between multiple goroutines anywhere.
The text was updated successfully, but these errors were encountered:
does your code have any of their own goroutines? maybe event get reference to http.ResponseWriter from contexts passed to them somehow? What does that LiveRelationsConfig.Get do?
I don't have any of my own goroutines, but I did notice yesterday that a custom middleware was moving a reference to the context to the main thread. I wasn't actually using it, but I've fixed that in hopes that that was the issue. I've found it pretty hard to trigger this specific crash though, it's only happened twice seemingly randomly (peak race condition fun)
It is very hard to tell anything specific - just search all the places you are calling c.Response() and doing something with it and asses if it could escape the previous request goroutine and/or lifetime of the request.
I'm not entirely sure what information you'd need to help diagnose this. As far as I can tell the panicking stacktrace doesn't go through any of my code, and I'm not (intentionally) sharing the context between multiple goroutines anywhere.
The text was updated successfully, but these errors were encountered: