Workaround #48

[ktf]

This adds a notmuch "unknown" tag whenever a label id which cannot be found
in the list of available label ids is retrieved from a message. Notice the
"unknown" tag is never synchronized.

[gauteh]

Thanks; good that you figured out a way to get around this. I don't think I want to merge this right away since there must be some other underlying error. Could you try to put in the offending label in https://developers.google.com/gmail/api/v1/reference/users/labels/get ? Maybe we have to manually fetch the label if it didn't get fetched the first time.

[gauteh]

If we can confirm that this is indeed a non-existant label, maybe it would be better to just not add anything and ignore it. It would possibly delete the label on the GMail side in the future so I think we should have a switch which allows this. It is likely to only be an issue on initial sync anyway. Then we can just advice the user to enable this switch if he/she wants.

[ktf]

Actually, the label is not there at all, neither in list, nor if I get it by id:

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "notFound",
    "message": "Not Found"
   }
  ],
  "code": 404,
  "message": "Not Found"
 }
}

other labels are actually there.

[ktf]

And if I look into the message itself, the label is actually there:

 "labelIds": [
  "Label_3",
  "CATEGORY_PERSONAL"
 ],

[gauteh]

Giulio Eulisse writes on november 17, 2017 0:18:

And if I look into the message itself, the label is actually there: ``` "labelIds": [ "Label_3", "CATEGORY_PERSONAL" ], ```

Hm, weird! This looks like a GMail bug. Do you want to report the issue there: https://issuetracker.google.com/ ? Not much hope in getting an answer, I already have one pending: https://issuetracker.google.com/issues/62686910

[ktf]

I will try. I am also trying to see if another route works better.

[gauteh]

Check out the approach in #51, does that work for you?

[gauteh]

Implemented through #51.

[ktf]

thanks. That's what I needed.