-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
KeyError: '15bac9a5ba0b826b' in update_tags: self.mids[mid] #25
Comments
I was just doing the usual sync thing. |
I guess the correct thing to do is to just re-download the message if it went missing on the local disk for some reason (not sure why it went missing in the first place, but that's a different story). |
A full sync fixed it, BTW. Maybe a full sync should be triggered automatically in such a case? Or maybe there should be a warning if the files are missing, but fetch them and continue (so that you can run a full sync eventually when you have time). |
If a message doesn't exist it is always fetched. Something went wrong in
this case, and it was not scheduled for fetching.
Did you first change labels of a message in web-ui and then delete a
message?
- gaute
|
OK, so the message was available on the remote side (queried the gid of the message via API explorer) and I'm not aware of me changing tags on it - maybe locally, but I don't recall touching the emails remotely. It only disappeared locally but I'm not sure why. |
OK, I'm digging through the history list. Meta info from my log was:
In revision 12103168, the message and several others received the
|
Ah no, there was an earlier failure:
I also just noticed that the trash label adding revision 12103168 is not the same as the one from the gmi output: 12103618. |
So the changes to that message on the remote side were:
I guess the culprit might be the +TRASH -TRASH pair in the same pull? |
Julian Andres Klode writes on juni 2, 2017 9:02:
So the changes to that message on the remote side were:
```
12103168 +TRASH
12103211 -TRASH
12103807 -Label_41
```
I guess the culprit might be the +TRASH -TRASH pair in the same pull?
Yes, good catch - I think that might result in a bug! And, we know how
to reproduce it!
|
I believe inside the |
Julian Andres Klode writes on juni 2, 2017 9:10:
I believe inside the ```if 'labelsRemoved' in h:``` case of Gmailiieer.partial_pull(), it checks ```# in case a not_sync tag has been added``` and removes stuff from added lists, and (re-)adds to the deleted list. But the not_sync tag has been removed there, not added, so it's the wrong way around AFAICT.
Yeah, I thought so first too - but then I remembered that the labelIds
field contains the current labels, not the labels that have been
removed (I think!).
- gaute
|
The gmail API fails with an error otherwise. fixes gauteh#25
The gmail API fails with an error otherwise. fixes gauteh#25
I had that issue again (with an email I archived remotely IIRC), and it started working again after I trashed and untrashed the message in question in the gmail web UI. |
I think this should no longer be an issue since TRASH and SPAM messages are synced. |
The text was updated successfully, but these errors were encountered: