Re: NoCeM flakiness in 0.74 and higher

[David Moore <dmoore@UCSD.EDU>]

Sudish Joseph <sudish@mindspring.com> writes:

> >> Here's where I stopped gnus:
> >> Checking article 25608 in alt.nocem.misc for NoCeM...
> >> Good signature from user "AutoMoose1 (Automated Cancelmoose)".
> >> Verifying...
> 
> > 	If it was stuck verifying, you could always (setq
> > gnus-nocem-verifier nil).  This is also substantially faster, at the
> > cost that someone might forge a nocem posting.
> 
> Oops, I should've been clearer.  It isn't hanging--it's reading
> articles that it's marked as read in NoCeM/active.  The entry for
> alt.nocem.misc in my orig post is ("alt.nocem.misc" (25378 . 26700)).
> But it's verifying article 25608 above.

	Oh, interesting.  I've not seen this happen and looking in the
code in 0.74 can't really see where it might be happening.
gnus-nocem-scan-groups should call gnus-retrieve-headers with 1+26700 to
26811 (the max active from nntp in this case).  Maybe it's not loading
your cache properly?  Anyone else seeing something like this?


-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | In a cloud bones of steel.