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
When an endpoint uses the timeout wrapper and panics, the stacktrace shown in the logs won't contain any reference to the actual line that caused the panic. I believe it happens because the controller code runs in a goroutine and thus the library can't know about where the panic originally happened.
Related: #36
When an endpoint uses the timeout wrapper and panics, the stacktrace shown in the logs won't contain any reference to the actual line that caused the panic. I believe it happens because the controller code runs in a goroutine and thus the library can't know about where the panic originally happened.
Stacktrace without timeout wrapper:
(Notice the lines starting with ~/project)
Stacktrace with timeout wrapper:
In this stacktrace, only the middlewares of my project are present and not the real source of panic.
The text was updated successfully, but these errors were encountered: