Catch the bad status line exception and log it

[laxdog]

Polo sometimes return a bad error code we can't parse. This catches that exception.

Description

Fixes #205

TESTING STAGE

Tested

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have read CONTRIBUTING.md
• I fully understand Github Flow.
• My code adheres to the code style of this project.
• [N/A] I have updated the documentation in /docs if I have changed the config, arguments, logic in how the bot works, or anything that understandably needs a documentation change.
• [N/A] I have updated the config file accordingly if my change requires a new configuration setting or changes an existing one.
• I have tested the bot with no issues for 24 continuous hours. If issues were experienced, they have been patched and tested again.

[rnevet]

1. It's not so clear why this needs special handling. (to prevent sleep?)
2. I'm not sure the handling is complete without persisting the status. (i.e. log.persistStatus())

I would suggest just adding:
elif isinstance(ex, BadStatusLine): // ignore
In the exception handler.

[laxdog]

1. No reason. I actually thought they were separated because the first ones were catching the class and the others were using the string.
2. I didn't realise that was required either.

Changed and pushed.

[rnevet]

Looks good to me, a bit of testing and it can be merged.

[chfast]

Should it go as a except BadStatusLine:?

[rnevet]

It could, but then we would need to duplicate the entire error logic that is in except Exception: already. (i.e. logging, status persisting, sleep)