Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recent frequent failures to pull #120

Closed
sten0 opened this issue Oct 29, 2019 · 3 comments
Labels

Comments

@sten0
Copy link

@sten0 sten0 commented Oct 29, 2019

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

@gauteh

This comment has been minimized.

Copy link
Owner

@gauteh gauteh commented Oct 29, 2019

Hi,

I am considering replacing this with a warning. We've had the hard fail in for ever, and it does not seem that we actually loose any information (even though a user would not necessarily notice that).

I haven't seen any new information from Google about the API behavior here. Any thoughts?

Regards, Gaute

@gauteh gauteh added the gmail-api label Oct 29, 2019
gauteh added a commit that referenced this issue Nov 3, 2019
@gauteh

This comment has been minimized.

Copy link
Owner

@gauteh gauteh commented Nov 3, 2019

Could you please try #121?

@gauteh gauteh closed this in f0b1bf9 Nov 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.