From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Trying to prune the registry because it's full; apply: registry max-size limit reached
Date: Mon, 30 Mar 2015 17:45:47 +0800 [thread overview]
Message-ID: <87pp7qn7hw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sicmq1ci.fsf@gnu.org>
Tassilo Horn <tsdh@gnu.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> Hi Eric,
>
>>> A few days ago I changed it so that it really did reach its max size
>>> before pruning. Obviously something isn't quite aligned right. I'm
>>> assuming some sort of off-by-one error: we're using #'< where we
>>> should be using #'<=, or something like that.
>>
>> Embarrassingly, that is indeed what was happening. Would you mind
>> giving this patch a whirl? If it works correctly, I'll push it (plus a
>> ChangeLog notice).
>
> I've switched back to 10000 max entries, and now
>
> (registry-full gnus-registry-db)
>
> returns t. I can enter groups and read messages without an error but I
> don't get any messages about pruning. But after reading a bunch of new
> messages now, (registry-full gnus-registry-db) gives nil and
> (registry-size gnus-registry-db) says 9007, so apparently it has pruned
> anyhow.
Okay, thanks. My guess is that the "Trying to prune the registry because
it's full" message is getting buried in other messages -- I don't see
how it could not be called. If you're really idle at the moment, could
you look in *Messages* and confirm that? But if you cut back to 10000
max entries and now have 9007, then things are almost certainly working
correctly.
Later on I'll make a new defvar (something like
`gnus-registry-pruning-functions') where third-party packages can
register pruning functions. That way, if a package registers a
"precious" key that cause entries to hang around, it can also register a
function for cleaning up after itself.
Thanks,
Eric
next prev parent reply other threads:[~2015-03-30 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 6:12 Tassilo Horn
2015-03-30 6:57 ` Eric Abrahamsen
2015-03-30 7:15 ` Eric Abrahamsen
2015-03-30 9:30 ` Tassilo Horn
2015-03-30 9:45 ` Eric Abrahamsen [this message]
2015-03-30 11:02 ` Tassilo Horn
2015-04-17 19:48 ` Ted Zlatanov
2015-04-18 3:22 ` Eric Abrahamsen
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=87pp7qn7hw.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.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).