-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic handling and stack trace don't work when GOPATH includes /go/
in it
#1287
Comments
ralfthewise
changed the title
Panic handling and stack trace don't work in typical docker usage
Panic handling and stack trace don't work when GOPATH includes Jan 7, 2018
/go/
in it
Thanks, will look into this |
Hi, as a hotfix I've tried:
To my surprise, both didn't help. Any further ideas at least for a hotfix? |
@djtm we were able to work around it with Dockerfiles starting off as such:
|
@ralfthewise: Thanks a lot! Did you get it to work with minimal images?
Still getting the same error however... |
Hi guys, sorry this fell through the cracks - is this still an issue in the later builds ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a typical setup of go with docker containers (using the official images at https://hub.docker.com/_/golang/) the GOPATH is setup to be
/go
. The first frame in a panic stack trace is almost always:The panic handling function
findRelevantStackFrame
(https://github.com/revel/revel/blob/master/errors.go#L128) has logic to find the first frame in the source path that isn't robust enough and ends up thinking/usr/local/go/src/runtime/debug/stack.go
is the first item because it contains/go/src
. This results in an actual panic in revel itself, no helpful stacktrace returned to the browser, and output like this:Somewhat related to #1266
The text was updated successfully, but these errors were encountered: