From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: nnfolder groups losing expirable marks
Date: Fri, 21 Jan 2011 14:50:30 -0500 [thread overview]
Message-ID: <87wrly594p.fsf@uwo.ca> (raw)
In-Reply-To: <87r5c9g4yn.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
> Using the Jan 4 version of git gnus (a1d4c9b50...) I'm finding that my
> expirable marks are very frequently being lost in nnfolder groups. It
> seems to happen whenever expiry is run: the articles that aren't old
> enough to be expired lose their expirable marks. But I haven't done
> enough experimenting to be sure this is the pattern.
I have now experimented some more, and this seems to be exactly the
pattern. It is 100% reproducible in nnfolder groups, by marking recent
articles as expirable and then running gnus-group-expire-articles on
the group.
> I checked the log of later commits and didn't see anything relevant,
> but I am happy to upgrade to the latest version if that would help.
I checked today's latest version and the problem is still there.
Moreover, I figured out that the problem starts exactly with this
commit:
commit 06eeefe0c892fd77f7a79493fa4f1db0f8058761
Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Date: Thu Dec 16 18:58:19 2010 +0100
Clear up nnml expiry target performance regressions.
Fix previous fix by having nnfolder save all its buffers
explicitly.
I'm hesitant to change this, though, since it seems this was done for a
reason. And I'm not sure what "previous fix" is being referred
to---probably it means the nnml fix.
In case it is relevant, I have nnfolder-marks-is-evil set to t and the
groups where I've noticed this are auto-expire groups.
Dan
next prev parent reply other threads:[~2011-01-21 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 23:36 Dan Christensen
2011-01-21 19:50 ` Dan Christensen [this message]
2011-01-22 3:22 ` Lars Ingebrigtsen
2011-01-22 3:38 ` Lars Ingebrigtsen
2011-01-23 0:56 ` Dan Christensen
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=87wrly594p.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).