{"push_id":1229525923,"size":1,"distinct_size":1,"ref":"refs/heads/crash-on-listener-goroutine-panic","head":"2fc95aa5a2671f79d00c348197b08883013743e8","before":"d158d819694e7540fc29a148e61ea18e847b8fb1","commits":[{"sha":"2fc95aa5a2671f79d00c348197b08883013743e8","author":{"name":"Marcin Ptaszyński","email":"81862be354ccac2735b45462436aeb4ebbfe0095@ntti3.com"},"message":"Crash on sync/snmp listener goroutine panic\n\nIf sync processing goroutine crashes for any reason, we should not\njust log panic and keep on going. In such case, Gohan is rendered\nunusable, but it doesn't go down completely, so it's not detectable.\n\nAnother problem is that in case of failure in any goroutines mentioned\nabove logging only error message is not sufficient for debugging.\n\nThis commit changes above behavior so in case of listener goroutine\npanic, it will log whole stacktrace and crash whole Gohan process.","distinct":true,"url":"https://api.github.com/repos/marcin-ptaszynski/gohan/commits/2fc95aa5a2671f79d00c348197b08883013743e8"}]}
{"actor":{"display_login":"marcin-ptaszynski"}}