Exiting a group with (all?) expiring articles is currently broken

Exiting a group with (all?) expiring articles is currently broken

[Karl Kleinpaste]

[-- Attachment #1: Type: text/plain, Size: 79 bytes --]

I have an nnml group "tomb" where spam goes to die.  It has these
properties:


[-- Attachment #2: tomb properties --]
[-- Type: text/plain, Size: 61 bytes --]

((banner . egroups)
 (total-expire . t)
 (expiry-wait . 0))


[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

As of a CVS update of about 20 minutes ago (this is Thursday evening,
9:30pm EDT), attempting to exit this group rewards me with this stack
trace:


[-- Attachment #4: tomb exit trace --]
[-- Type: text/plain, Size: 974 bytes --]

Signaling: (wrong-type-argument number-char-or-marker-p >)
  <(> 8736)
  sort((8740) <)
  nnml-request-expire-articles((8736 8737 8738 8739 8740) "tomb" "" nil)
  gnus-request-expire-articles((8736 8737 8738 8739 8740) "tomb")
  gnus-summary-expire-articles()
  run-hooks(gnus-summary-expire-articles)
  apply(run-hooks gnus-summary-expire-articles)
  gnus-run-hooks(gnus-summary-prepare-exit-hook)
  gnus-summary-exit(t)
  gnus-summary-next-group(nil "archive.current.personal.slaves" nil)
  gnus-summary-next-article(t "$2000 Weekly Possible Stuffing Envelopes at Home!!")
  #<compiled-function nil "...(73)" [gnus-newsgroup-data gnus-auto-select-same gnus-summary-goto-unread headers to gnus-summary-next-article never gnus-summary-last-article-p get-text-property gnus-intangible gnus-summary-goto-subject gnus-number gnus-summary-last-subject 3 vectorp 1] 7 ("/home/karl/Emacs/Gnus/gnus-sum.elc" . 179250) nil>()
  call-interactively(gnus-summary-next-unread-article)


[-- Attachment #5: Type: text/plain, Size: 230 bytes --]

The articles are not deleted, though enough internal updating has
occurred that I can force exit with `Q' and find that the articles are
considered to have been read.  That is, the *Group* buffer shows `0'
after exiting with `Q'.

Re: Exiting a group with (all?) expiring articles is currently broken

[Henrik Enberg]

Karl Kleinpaste <karl@charcoal.com> writes:

[...]

> The articles are not deleted, though enough internal updating has
> occurred that I can force exit with `Q' and find that the articles are
> considered to have been read.  That is, the *Group* buffer shows `0'
> after exiting with `Q'.

I have roughly the same problem, I don't get any errors but when I exit
groups with expiry-target (and only those groups) set all remaining
articles gets marked as ancient (`O') instead of expirable (`E'). This
is probably somehow related to Andrew Innes changes on 2001-08-30, those
are atleast the only changes made between my last update where it did
work and now.

Henrik
-- 
Could I have a drug overdose?

Re: Exiting a group with (all?) expiring articles is currently broken

[Karl Kleinpaste]

Karl Kleinpaste <karl@charcoal.com> writes:
> As of a CVS update of about 20 minutes ago (this is Thursday evening,
> 9:30pm EDT), attempting to exit this group rewards me with this stack
> trace:

> Signaling: (wrong-type-argument number-char-or-marker-p >)
>   <(> 8736)
>   sort((8740) <)
>   nnml-request-expire-articles((8736 8737 8738 8739 8740) "tomb" "" nil)

I investigated a bit, and found that the problem was a corrupt
overview in tomb.  It somehow had been abused so that the first line
in the file was this:

>		12085	315	Xref: cinnamon.vanillaknot.com tomb:8708	To: <cola55@freeze.com>	Keywords: font,color,face,arial,size,align,&nbsp,height,narrow,#000000,div,width,left,span,name,#008000,right,center,input,style,sans-s,helvetica,erif,bgcolor,background-color	

Evidently, a previous exit from tomb had not done a proper & clean job
of expiring articles, having left a partial entry for article 8708
(see Xref content) at the top of the file.

Article 8708 in this spam-catcher group must have been from a week or
more ago, and I wonder how this worked at all since that time.

The rest of the overview was fine, containing normal entries for 8736
through 8740.  Deleting the offending fragmentary line made it work
again, and all is well: All articles were expired, the articles are
gone, and the overview is now empty.

I am concerned that some recent change seems to have damaged article
expiry so as to abuse overviews.

Re: Exiting a group with (all?) expiring articles is currently broken

[Karl Kleinpaste]

Karl Kleinpaste <karl@charcoal.com> writes:
| It somehow had been abused so that the first line
| in the file was this:

| >		12085	315	Xref: cinnamon.vanillaknot.com tomb:8708	To: <cola55@freeze.com>	Keywords: font,color,face,arial,size,align,&nbsp,height,narrow,#000000,div,width,left,span,name,#008000,right,center,input,style,sans-s,helvetica,erif,bgcolor,background-color	

I wanted to followup once more to make something clear: The damaged
line, as erroneously left in the overview, began with a greater-than
character, which is why several calls were failing on "not an integer"
errors.  That is, I wasn't weirdly "quoting" an overview file; that's
what was /in/ the overview file, from the trailing end of the
"references" content.