{"push_id":771116023,"size":2,"distinct_size":1,"ref":"refs/heads/develop","head":"dc5c90a6636cbb14c60b43e2023b98e16cfa60f5","before":"e0410cdd30b4bb09b3e852625bb3ad7c6007e879","commits":[{"sha":"82b3f5aac87bf8cd44f17016673380d8647172b2","author":{"email":"bcd66b84ebceb8404db9191d837c83f1b20bab8e@redhat.com","name":"Ralph Bean"},"message":"Handle some errors from the captcha generator.\n\nThe main case here is where we handle HTTPGone.  The vast majority of our\nproduction tracebacks are from here where (somehow) people are loading forms\nthat generate captchas (which works) and then way later, they are requesting\nthose same captcha images again (over 300 seconds later.. that's like 5\nminutes). I *bet* this is happening if someone has a bodhi update page open,\nand then their browser crashes and tries to restore its previous state, or\nsomething like that.\n\nAnyways, this patch adds a catch to that main \"captcha is expired\"\n``InvalidToken`` traceback that is spamming our logs.  It turns it into a 410\nGone statuscode, which makes sense. While testing it, I tried passing in\ngarbage which generated a different ``TypeError`` from the base64 module, so I\ncaught that too.\n\nFixes #237.","distinct":false,"url":"https://api.github.com/repos/fedora-infra/bodhi/commits/82b3f5aac87bf8cd44f17016673380d8647172b2"},{"sha":"dc5c90a6636cbb14c60b43e2023b98e16cfa60f5","author":{"email":"bbe0e0c7f494396f37b45b909d488cd5f21b7dc1@redhat.com","name":"Luke Macken"},"message":"Merge pull request #378 from fedora-infra/feature/captcha-errors\n\nHandle some errors from the captcha generator.","distinct":true,"url":"https://api.github.com/repos/fedora-infra/bodhi/commits/dc5c90a6636cbb14c60b43e2023b98e16cfa60f5"}]}