Fix for Issue 166

[digitalsleuth]

The error identified in #166 is caused when attempting to log e.message, however e does not actually have an attribute message. This PR removes the .message from the call to e, resolving the issue. Solution here is originally credited to the author of the issue.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[digitalsleuth]

@tinajohnson As discussed, any chance you can review this?

[tinajohnson]

Hey @digitalsleuth,
Thanks for the PR. We would want to fix all occurrences of this error-prone code in the codebase. Would you be able to work on them? If not, I am happy to take over.

[digitalsleuth]

Hi @tinajohnson , I wouldn't be opposed to helping out, however I don't have as much of a familiarity with the entirety of the code as you or someone else might have. If it's simply a matter of removing .message from each instance of e, that can be done, but testing each function to confirm the attribute is not needed would take some time.

Do you have any tests which execute each function already available to that I might be able to use to test with?

Aside from that, I do have another PR in the chamber ready to submit for another error, but I wanted to wait until I could get fakenet running again with this PR before I submit any others.

[digitalsleuth]

Hi @tinajohnson , I've reviewed the similar calls to e.message throughout and replaced them with str(e) instead to provide the proper error output.