[Thread Failure] 'ascii' codec can't decode byte 0xe2 in position 120: ordinal not in range(128)

I'm getting this when running:

`s4cmd dsync -r --verbose /Volumes/Volume_Name-1/Foo_Bar_Project/ s3://dir01/archive/Foo_Bar_Project/`

I'm running on OS X 10.11.5 El Capitan (I know, it's what I have available at this moment in time) I have admin privileges, and I can verify that PIP, Brew, Python - they're all up to date.

When running in verbose, I can see that it is actually going through and verifying wether an object has been previously synced. I started this transfer with CyberDuck and it timed out at the end, oddly enough, but with no specific error.

Has anyone ran into a similar problem in their workflow?

Start by reproducing the reported s4cmd dsync command with --verbose on the stated OS X/Python environment, then trace the verbose object-verification and thread-failure path. Done means the reported non-ASCII filename or object can be processed without the ASCII decoding error.

Written by the indexing model from the issue text.