From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/3114 Path: news.gmane.org!not-for-mail From: Kevin Greiner Newsgroups: gmane.emacs.gnus.user Subject: Re: gnus-agent-expire detected a missing NOV entry Date: Tue, 21 Oct 2003 21:29:02 -0500 Message-ID: References: <86k772pcx2.fsf@doze.rijnh.nl> <86u165obyc.fsf@doze.rijnh.nl> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1138669319 17666 80.91.229.2 (31 Jan 2006 01:01:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:01:59 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:31:43 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: dialup-216-12-206-111.ev1.net Original-X-Trace: quimby.gnus.org 1066789763 2505 216.12.206.111 (22 Oct 2003 02:29:23 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: Wed, 22 Oct 2003 02:29:23 +0000 (UTC) User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (windows-nt) Cancel-Lock: sha1:7X9fwbfsBHGmHORPoABR9ugsT4k= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:3255 Original-Lines: 44 X-Gnus-Article-Number: 3255 Tue Jan 17 17:31:43 2006 Xref: news.gmane.org gmane.emacs.gnus.user:3114 Archived-At: Jochen Küpper writes: > On Sun, 19 Oct 2003 01:59:44 +0200 Simon Josefsson wrote: > > Simon> If it isn't a bug, at least those messages should use a higher > Simon> gnus-verbose setting so they don't clutter the screen all the > Simon> time. > > It's actually not only cluttering the screen, but really a performance > problem. After a while I get easily several tens (even hundreds) of > these messages per B m'ed message; if I then move 5 or ten messages > somewhere else you recognize that it takes longer than without these > warnings. (This might be Cygwin specific?) > > Simon> No idea on fixing it though. > > Well, somehow the agent seems to miss the removal of messages; maybe > there is already functionality to do that for a single message? gnus-agent-expire has a force option that is used in one place to remove single articles. I need to see how nnimap is handling this operation to understand why the agent is getting corrupted. > Maybe calling gnus-agent-regenerate-group after removing an article > From agentized groups is not too much of a hog? That's probable, group regeneration was written to recover from errors and not as a tool to cheaply sync the agent with a back end. In this particular case, some function apparently deleted the agent's local article file without also updating agent's internal data structures. That's why the gnus-verbose setting on these messages is so low. The agent is reporting data integrity errors that the agent is now having to correct. If you didn't see these messages, and complain about them, I'd never get this cleaned up. The 'B m' command is bound to gnus-summary-move-article but it doesn't invoke the agent directly. Could either of you set debug-on-entry on gnus-agent-expire-group-1 then post the stack trace. That will help me isolate where the error is likely to have occurred. In the meantime, I'll see if I can set up an imap environment where I can duplicate this error. Kevin