{"push_id":3042246762,"size":1,"distinct_size":1,"ref":"refs/heads/eofExceptionIssue","head":"2091d2ca10969f172fa0864289227358e1b0e97c","before":"d2283431971a53ecdc19131e9c941f8fc821aa29","commits":[{"sha":"2091d2ca10969f172fa0864289227358e1b0e97c","author":{"name":"Shail Patel","email":"a92d44be3f771c286015ed45b6bd06b41e18135b@uber.com"},"message":"Catch EofException at the jetty handler level\n\nThis change is meant to address https://github.com/dropwizard/dropwizard/issues/2482\n\nBecause the EofException is thrown when the handler is trying to write the response, an exception mapper can't solve this issue. In the future, for a more robust solution, we should allow logging levels to be configurable here.","distinct":true,"url":"https://api.github.com/repos/shail/dropwizard/commits/2091d2ca10969f172fa0864289227358e1b0e97c"}]}
{"actor":{"display_login":"shail"}}