-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Kevin's local build directory being shown? #21
Comments
Hi @exegeteio, it’s default Go behaviour to include the source paths in stack traces during a panic. I don’t think it’s really a problem in this case, but I agree it can be surprising. I’ll update the makefile to trim those paths out of the release builds (there’s a compiler flag to do that). Thanks for bringing this up! |
Oops sorry, missed that part on first read! If you fancy taking a stab at this, take a look at the |
@exegeteio I've also added #22, for the related issue that we shouldn't be showing a stack trace in this situation anyway (regardless of what's in that stack trace). |
It appears that the folder on @kevinmcconnell 's machine where the app was built is being output when the go app errors out:
The text was updated successfully, but these errors were encountered: