ignore bson unicode decode error

[islue]

I met such an error and the backup process hung.

[2017-05-11 04:18:47,505] [CRITICAL] [MongodumpThread-5] [Oplog:load:55] Error reading oplog file /var/lib/mongodb-consistent-backup/mytable/20170511_0256/ps-rs1/dump/oplog.bson! Error: 'utf8' codec can't decode byte 0xa1 in position 0: invalid start byte
[2017-05-11 04:18:47,505] [ERROR] [MongodumpThread-5] [MongodumpThread:run:121] Error loading oplog: 'utf8' codec can't decode byte 0xa1 in position 0: invalid start byte
Traceback (most recent call last):
  File "/var/lib/mongodb-consistent-backup/.pex/install/mongodb_consistent_backup-1.0.1-py2-none-any.whl.50d2483f9d3c33ae9bb528471e56ca495b2758f3/mongodb_consistent_backup-1.0.1-py2-none-any.whl/mongodb_consistent_backup/Backup/Mongodump/MongodumpThread.py", line 119, in run
    oplog.load()
  File "/var/lib/mongodb-consistent-backup/.pex/install/mongodb_consistent_backup-1.0.1-py2-none-any.whl.50d2483f9d3c33ae9bb528471e56ca495b2758f3/mongodb_consistent_backup-1.0.1-py2-none-any.whl/mongodb_consistent_backup/Oplog/Oplog.py", line 56, in load
    raise OperationError(e)
OperationError: 'utf8' codec can't decode byte 0xa1 in position 0: invalid start byte

I'm not sure if it is caused by invalid bson data, but it corrupted the backup anyway. Since the codes show only 'ts' is concerned, I suppose that ignoring the error is ok. How to you think?

I ran the patched version and it worked for me.

References:
https://jira.mongodb.org/browse/PYTHON-721

[timvaillancourt]

Thanks @islue, this is a good idea. I pulled this into our 1.0.2 branch under PR #130.

After successful testing of 1.0.2 it will become 'master' so I will close this PR now.