Recent frequent failures to pull #120
Description
Hi @gauteh !
I've been running into the following deal-breaker bug more and more frequently, and I've confirmed it affects both 0.10 and 0.11. After an undefined period of time it appears to work again, but it doesn't seem to be triggered by frequency of syncs, so I don't think it's some kind of google-side rate-limiting issue.
$ gmi --logging_level DEBUG pull
pull: partial synchronization.. (hid: 20177555)
fetching changes: 0it [00:00, ?it/s]remote: no 'history' when more pages were indicated.
remote: request failed, increasing delay between requests to: 1 s
pull: failed, re-try in a bit.
fetching changes: 100it [00:00, 1182.09it/s]
Traceback (most recent call last):
File "/usr/bin/gmi", line 8, in <module>
g.main ()
File "/usr/share/gmailieer/lieer/gmailieer.py", line 155, in main
args.func (args)
File "/usr/share/gmailieer/lieer/gmailieer.py", line 351, in pull
self.partial_pull ()
File "/usr/share/gmailieer/lieer/gmailieer.py", line 360, in partial_pull
for hist in self.remote.get_history_since (self.local.state.last_historyId):
File "/usr/share/gmailieer/lieer/remote.py", line 203, in get_history_since
raise Remote.NoHistoryException ()
lieer.remote.NoHistoryException
Any guidance for how to make this report more useful would be welcome :-)
Cheers,
Nicholas