{"push_id":1317928388,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"01231aef18015f135b6c9b43ce5298758132414a","before":"ff9bd0446aa9f6ac9926f6d3b546f0fec65254e4","commits":[{"sha":"436fb8b0b670381b7d16bf0fd0670cb0aea784b3","author":{"name":"Daniel Thayer","email":"fc8e0f0d1e0980cece41a977c55954bb76e77425@illinois.edu"},"message":"Don't show a stack trace when it's not useful\n\nBroControl exceptions are now defined in the new exceptions.py file.\nThe broctl client will handle only those exceptions (showing a useful\nerror message), because they are expected to occur in various\npredictable situations (bad user input, bad config file, etc.).\nIn these situations, a stack trace is not useful, because the cause\nof the problem is well-understood (and should be explained by the\nerror message).\n\nIf a standard Python exception is raised (this is not expected to occur),\nthen broctl will terminate with a stack trace, which is useful to help\ndebug the problem.","distinct":false,"url":"https://api.github.com/repos/bro/broctl/commits/436fb8b0b670381b7d16bf0fd0670cb0aea784b3"},{"sha":"01231aef18015f135b6c9b43ce5298758132414a","author":{"name":"Justin Azoff","email":"7f1bebfc8f3d53988a6b50b7e5d068197c83e7dc@gmail.com"},"message":"Merge remote-tracking branch 'remotes/origin/topic/dnthayer/ticket1677'\n\n* remotes/origin/topic/dnthayer/ticket1677:\n  Don't show a stack trace when it's not useful","distinct":true,"url":"https://api.github.com/repos/bro/broctl/commits/01231aef18015f135b6c9b43ce5298758132414a"}]}
{"actor":{"display_login":"bro-bot"}}