From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: gcc-mark-as-read sometimes broken on Exchange
Date: Tue, 07 Dec 2010 13:15:53 -0500 [thread overview]
Message-ID: <84oc8x8n52.fsf@davestoy.home> (raw)
In-Reply-To: <84sjy9909t.fsf@davestoy.home> (Dave Goldberg's message of "Tue, 07 Dec 2010 08:32:14 -0500")
>> Oh! I asked you to eval something, and you did. Tee hee. Never mind.
>> But try evaling this:
>> (nnimap-request-accept-article "INBOX" "cyrus")
> This works properly with both cyrus and exchange. The return is a
> cons of the folder name and resulting article number. No matter how
> many times I run it, I never get nil. I'll try stepping through
> gnus-inews-do-gcc and see if I can find the glitch.
OK, it took a long time (especially since stepping through every gcc with edebug, and then figuring out which functions to edebug-defun) to actually hit the problem and again it only happens on occasion with the Exchange server, but after several dozen gcc's I finally hit the bug. The problem shows up around the bottom of nnimap-request-accept-article.
After successfully appending the article into the group, we get to this code:
(cons group
(or (nnimap-find-uid-response "APPENDUID" (car result))
(nnimap-find-article-by-message-id
group message-id)))))))))
And both return nil. Unfortunately, I'm not sure which one is returning successfully when it does work because I wasn't stepping through nnimap-request-accept-article at the time. I'll keep stepping through everything but it seems that it takes several tries before I hit the bug, once I do I hit it all the time. On the plus side, I now know exactly which function to debug so I'll save a bit of time with further stepping.
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2010-12-07 18:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 19:10 Dave Goldberg
2010-12-01 17:15 ` Lars Magne Ingebrigtsen
2010-12-06 20:53 ` Dave Goldberg
2010-12-06 22:24 ` Lars Magne Ingebrigtsen
2010-12-07 13:32 ` Dave Goldberg
2010-12-07 18:15 ` Dave Goldberg [this message]
2010-12-07 18:24 ` Dave Goldberg
2010-12-07 22:11 ` Dave Goldberg
2010-12-08 19:50 ` Dave Goldberg
2010-12-09 22:59 ` Lars Magne Ingebrigtsen
2010-12-10 16:47 ` Dave Goldberg
2010-12-16 16:35 ` Lars Magne Ingebrigtsen
2010-12-16 22:46 ` Dave Goldberg
2010-12-17 0:08 ` Tibor Simko
2010-12-17 16:37 ` Lars Magne Ingebrigtsen
2010-12-21 0:01 ` Tibor Simko
2010-12-17 16:35 ` Lars Magne Ingebrigtsen
2010-12-21 0:12 ` Tibor Simko
2011-01-02 6:59 ` 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=84oc8x8n52.fsf@davestoy.home \
--to=david.goldberg6@verizon.net \
--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).