Catch previously uncaught exception

[mymatenige]

There is an exception being thrown that is not currently caught in the code. Under high resource usage I can receive the following exception. I've made a fix that resolves this. I've tried to keep the fix inline with existing handling within the codebase.

Example stack trace below. Line numbers may not match entirely due to local edits.

Traceback (most recent call last):
  File "/usr/local/bin/dropbox", line 646, in __readline
    toret = self.f.readline().rstrip("\n")
  File "/usr/lib64/python3.7/socket.py", line 589, in readinto
    return self._sock.recv_into(b)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/dropbox", line 1597, in <module>
    ret = main(sys.argv)
  File "/usr/local/bin/dropbox", line 1586, in main
    result = commands[argv[i]](argv[i+1:])
  File "/usr/local/bin/dropbox", line 746, in newmeth
    return meth(*n, **kw)
  File "/usr/local/bin/dropbox", line 1014, in filestatus
    status = dc.icon_overlay_file_status(path=fp).get('status', ['unknown'])[0]
  File "/usr/local/bin/dropbox", line 717, in __spec_command
    return self.send_command(str(name), kw)
  File "/usr/local/bin/dropbox", line 674, in send_command
    ok = self.__readline() == "ok"
  File "/usr/local/bin/dropbox", line 648, in __readline
    raise DropboxCommand.BadConnectionError()
__main__.BadConnectionError

[nikhilm]

Duplicate of #89

[mymatenige]

@nikhilm #88 is not a duplicate of #89. The exception is thrown from a different place and the fix is different. Can you please re-review #88?

[nikhilm]

My apologies. The title and the stack were very similar. Thanks!

[mymatenige]

Brilliant - thank you!