Closed rvillablanca closed 4 years ago
Maybe @strk could give some help.
Someone with access to the logs can tell what paniced...
@strk Where could we send an issue for package strk.kbt.io/projects/go/libravatar
?
It seems a lock is need for that map read and write.
On Thu, Aug 15, 2019 at 06:11:07AM -0700, Lunny Xiao wrote:
@strk where we could send an issue for package
strk.kbt.io/projects/go/libravatar
?
As written to that web page: to my email address, or to the gitlab mirror.
Is there any possibility to catch this panic ?
It should be an upstream library problem.
It should be an upstream library problem.
I agree with this, it is a known library problem but it is also shutting down gitea. I think this should be logged and handled in every request by default in all http handlers. Is it allowed for an unhandled panic to crash the whole app ?
@lunny @strk I've just filed a PR in go-libravatar to address this.
[x]
):https://gist.github.com/rvillablanca/16ca66169dd2c2ddf72bcf9afb5f511e
Description
Gitea just crashed. I don't know how this happened but it seems related with gravatar library.
Screenshots
No screenshots