-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
Too many read 0, while fetching msg '214' #292
Comments
Which version? |
6.5.6, under NetBSD 7.0. |
Please, try latest stable. |
In latest stable (6.6.1) I had a filesystem crash and if I delete the entire folder and download everything again it works, but I believe OfflineIMAP was supposed to handle this or provide more useful error messages? Thanks! |
This |
list.remove(x): x not in list
due to poor error handling
Hi again! Thanks! I found and deleted problematic messages using the webmail. Isn't strange, though, that they "appeared" there? Is there any chance that offlineimap have pushed zero size or corrupted messages? Thanks! |
Yes, that's possible. We can't tell without samples to retry. |
Exactly the same same error happens on some mails when using Python 3, yet offlineimap under Python 2 works like a charm.
Looks like a socket cannot be polled in while not (terminate or self.Terminate):
if self.state == LOGOUT:
timeout = 10
else:
timeout = read_poll_timeout
try:
r = poll.poll(timeout)
if __debug__: self._log(5, 'poll => %s' % repr(r))
if not r:
continue # Timeout EDIT: Could be some encoding issue? |
I wonder that with Py3 the reader makes excessive reads while the full email got already downloaded if the recorded size of what was downloaded is wrongly too low. IOW, the email is already fully downloaded but the client didn't count the bytes correctly so it tries to read more data. This is just an idea that could really be wrong. |
Additional note: this could happen because |
I hit this issue on a F28 machine. It ran for a while, and then all of a sudden it now dies after a few minutes.
|
@purcell open a new issue, please. You're running on python2. |
@nicolas33 I think you meant to tag @purpleidea, not me. :-) |
Hello, I think this bug could be closed. If you run offlineimap with Python2 this error should not happen. If you run Python3, please, use offlineimap3. Regards, |
Hi there! In another
list.remote(x)
bug report (#198), you told me that the problem I reported was due to poor error handling and wasn't related to the other problem handled there. You then asked me to open a new issue. Here we go. Debug output is attached. Thanks!debug.txt
The text was updated successfully, but these errors were encountered: