KeyError on del.diskr2l[ruid] in cachemessagelist

[tmmorin]

General informations

• system/distribution (with version): Debian unstable
• offlineimap version (offlineimap -V): offlineimap v7.0.14, imaplib2 v2.55 (system), Python v2.7.13
• Python version: 2.7.13
• server name or domain: (internal)
• CLI options: offlineimap -a Exchange

Configuration file offlineimaprc

[general]
accounts = Exchange
pythonfile = ~/.offlineimap/myfunctions.py
maxsyncaccounts = 2
ssl=no

[Account Exchange]
localrepository = Local
remoterepository = Remote
autorefresh = 1
status_backend = sqlite

[Repository Local]
type = IMAP
remotehost = localhost
remoteuser = redacted
remotepasseval = get_password("localhost","redacted")
singlethreadperfolder = yes
maxconnections = 12
holdconnectionopen = yes
ssl = False

[Repository Remote]
type = IMAP
remotehost = redacted
remoteuser = redacted
remotepasseval = get_password("redacted","redacted")
singlethreadperfolder = yes
maxconnections = 8
folderfilter = lambda folder: folder == "INBOX" or folder == "unsync" or folder.startswith('unsync/') or ("ments envoy" in folder)
nametrans: lambda folder: (((folder == "INBOX") or ("ments envoy" in folder) )and folder) or re.sub(r'^', r'INBOX.', folder) 
holdconnectionopen = yes
ssl = False

Logs, error

2017-03-22 09:30:50 Folder INBOX [acc: Exchange]:
2017-03-22 09:30:50  ERROR: ERROR in syncfolder for Exchange folder INBOX: Traceback (most recent call last):
2017-03-22 09:30:50   File "/usr/local/lib/python2.7/dist-packages/offlineimap/accounts.py", line 604, in syncfolder
2017-03-22 09:30:50     localfolder.cachemessagelist()
2017-03-22 09:30:50   File "/usr/local/lib/python2.7/dist-packages/offlineimap/folder/UIDMaps.py", line 145, in cachemessagelist
2017-03-22 09:30:50     del self.diskr2l[ruid]
2017-03-22 09:30:50 KeyError: 3243210
2017-03-22 09:30:50 
2017-03-22 09:30:50   3243210

Steps to reproduce the error

• probably started to happen when I moved a lot of emails (hundreds) from INBOX on Local, to another folder on Local
• when the error started I was running offlineimap 7.0.12 (debian package)
• same error now repeats at each run, with the same ruid (3243210), whether I run 7.0.12 or 7.0.14
• I also tried with/without singlethreadperfolder = yes but it makes no difference

Since I can't sync anything in INBOX anymore, a workaround would be much appreciated !

[nicolas33]

Please, try the above version. The urgent patch I wrote will ignore the error and continue the work.

I'm surprised we hit this error. I wonder the UIDMaps file could be broken in some way. I'd say this might happen after a previous interrupted run (not necessarily the one before).

This would still need more digging to get what's happening exactly and check if we can be better at handling this error.

[tmmorin]

Thanks for the very quick fix. I was shy to do such a blunt workaround myself, unsure what the side effect on internal consistency could be.

Let me know if I can help understanding the root issue.

[nicolas33]

unsure what the side effect on internal consistency could be.

Actually, I didn't even tried to guess the side effects: the code fails at deleting a key that is missing. Either it was already removed (not likely) or it is missing from the collection since the beginning (more likely). So, ignoring this error shouldn't hurt. The UIDMaps file will be rewritten with the new data during the next run.

It's not clear to me from the above comment: did the patch help/fix your issue?> unsure what the side effect on internal consistency could be.

Actually, I didn't even tried to guess the side effects: the code fails at deleting a key that is missing. Either it was already removed (not likely) or it is missing from the collection since the beginning (more likely). So, ignoring this error shouldn't hurt. The UIDMaps file will be rewritten with the new data during the next run.

It's not clear to me from the above comment: did the patch help/fix your issue?

[tmmorin]

Sorry, yes the issue is fixed. The first run with the fix and the following ones were ok.

…

-Thomas

---- Nicolas Sebrecht a écrit ---- unsure what the side effect on internal consistency could be. Actually, I didn't even tried to guess the side effects: the code fails at deleting a key that is missing. Either it was already removed (not likely) or it is missing from the collection since the beginning (more likely). So, ignoring this error shouldn't hurt. The UIDMaps file will be rewritten with the new data during the next run. It's not clear to me from the above comment: did the patch help/fix your issue?> unsure what the side effect on internal consistency could be. Actually, I didn't even tried to guess the side effects: the code fails at deleting a key that is missing. Either it was already removed (not likely) or it is missing from the collection since the beginning (more likely). So, ignoring this error shouldn't hurt. The UIDMaps file will be rewritten with the new data during the next run. It's not clear to me from the above comment: did the patch help/fix your issue? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#445 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGhaKKPI7n7-1HneAGR2UdHI_na5Gfjyks5roQt6gaJpZM4Mk4Mw>.

_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

[nicolas33]

Ok, thank you.