Gnus development mailing list
 help / color / mirror / Atom feed
From: Didier Verna <didier@xemacs.org>
To: ding@gnus.org
Subject: Re: recent problem with IMAP counts
Date: Tue, 29 Nov 2011 10:14:38 +0100	[thread overview]
Message-ID: <muxk46js329.fsf@xemacs.org> (raw)
In-Reply-To: <muxk46jibqc.fsf@xemacs.org> (Didier Verna's message of "Tue, 29 Nov 2011 09:17:31 +0100")


       I found the culprit. The culprit is:

didier(pts/0)% git log -1 -p -r 90c1f88e5357d61a732d6f78d3c9a0278d78f49e
commit 90c1f88e5357d61a732d6f78d3c9a0278d78f49e (refs/bisect/bad)
Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Date:   Thu Jun 30 01:09:38 2011 +0200

    Bail out in nnimap if the server has closed the connection.

diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index 2cfc889..e78c20b 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -1227,6 +1227,10 @@ textual parts.")
 
 (deffoo nnimap-finish-retrieve-group-infos (server infos sequences)
   (when (and sequences
+            ;; Check that the process is still alive.
+            (get-buffer-process (nnimap-buffer))
+            (memq (process-status (get-buffer-process (nnimap-buffer)))
+                  '(open run))
             (nnimap-possibly-change-group nil server))
     (with-current-buffer (nnimap-buffer)
       ;; Wait for the final data to trickle in.


But in fact, the problem is more complicated than I thought. I
eventually figured out that it's one of my nnimap servers that causes
the problem, and the problem exhibits different symptoms before and
after this revision of Gnus. I have two nnimap servers in Gnus (one on
gmail, the other somewhere else; I think it uses Zimbra).

Before this revision of Gnus, it sync'ed with gmail all right at
startup, and then it hung on the other server. The minibuffer displayed
"Retrieving ... [0%]" flashing and blinking all over the place. I had to
C-g on it and only then got my Group buffer. The gmail account had the
correct info, but not the other one.

Now, with the current HEAD, Gnus startup doesn't hang anymore, but none
of the servers get the correct information. If I remove the problematic
server from my secondary select methods, everything's fine again.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com



  reply	other threads:[~2011-11-29  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28  9:21 Didier Verna
2011-11-28 10:21 ` Steinar Bang
2011-11-28 11:20   ` Didier Verna
2011-11-28 12:21 ` Eric S Fraga
2011-11-29  6:28   ` Giuseppe 'ferdy' Miceli
2011-11-29  8:17   ` Didier Verna
2011-11-29  9:14     ` Didier Verna [this message]
2011-11-29 16:39       ` Steinar Bang
2012-01-03 21:22       ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=muxk46js329.fsf@xemacs.org \
    --to=didier@xemacs.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).