Agent giving wrong info after gnus-agent-regenerate

Agent giving wrong info after gnus-agent-regenerate

[Kai Großjohann]

I ran gnus-agent-regenerate, and now the Agent is giving me wrong
data about some groups in the group buffer.  After M-g on them, the
unread count goes back from 10,000 (say) to 0.

(Actually, I don't know that the Agent is giving the wrong data: I'm
plugged.  But it started to happen immediately after
gnus-agent-regenerate, I'm sure.)

What can I do to help investigate the problem?
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

Re: Agent giving wrong info after gnus-agent-regenerate

[Kevin Greiner]

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> I ran gnus-agent-regenerate, and now the Agent is giving me wrong
> data about some groups in the group buffer.  After M-g on them, the
> unread count goes back from 10,000 (say) to 0.
>
> (Actually, I don't know that the Agent is giving the wrong data: I'm
> plugged.  But it started to happen immediately after
> gnus-agent-regenerate, I'm sure.)
>
> What can I do to help investigate the problem?

Well, the gnus-agent-regenerate-group can call
gnus-make-ascending-articles-unread if REREAD is non-nil.  On the
opposite end, gnus-agent-expire-group will update the agent's active
range.  Finally, gnus-select-newsgroup will expand the active range to
include articles found in the agent but no longer in the server's
active range.

I hope that that helps.  I'm not at all sure how the agent could would
make the unread count drop to zero.

Kevin

Re: Agent giving wrong info after gnus-agent-regenerate

[Kai Großjohann]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> I hope that that helps.  I'm not at all sure how the agent could would
> make the unread count drop to zero.

Oh, I see.  I explained it wrong.

Zero is the correct unread count.  So until I do `M-g' in plugged
mode, the unread count is wrong (too high).
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

Re: Agent giving wrong info after gnus-agent-regenerate

[Kevin Greiner]

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> I hope that that helps.  I'm not at all sure how the agent could would
>> make the unread count drop to zero.
>
> Oh, I see.  I explained it wrong.
>
> Zero is the correct unread count.  So until I do `M-g' in plugged
> mode, the unread count is wrong (too high).

Take a close look at gnus-agent-regenerate.  In particular, the code
just after the call to gnus-agent-regenerate-group.  That code expands
the group's active range to include any articles that are cached.

Kevin

Re: Agent giving wrong info after gnus-agent-regenerate

[Kai Großjohann]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> Take a close look at gnus-agent-regenerate.  In particular, the code
> just after the call to gnus-agent-regenerate-group.  That code expands
> the group's active range to include any articles that are cached.

I will investigate closer later, but what I can say is that the group
nnimap+dtm:ir.announce is not mentioned in ~/News/cache/active, and
there is no directory that corresponds to it, either.

It shows 2299 unread (and new) messages, 0 ticked, 2 dormant.  After
M-g, it shows 0 new, 0 ticked, 2 dormant.  Hitting RET on it (after
M-g), it asks me whether I want 773 messages.

I've now marked the two dormant messages as read.  We'll see what
happens when I start Gnus the next time.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

Re: Agent giving wrong info after gnus-agent-regenerate

[Kai Großjohann]

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Take a close look at gnus-agent-regenerate.  In particular, the code
>> just after the call to gnus-agent-regenerate-group.  That code expands
>> the group's active range to include any articles that are cached.
>
> I will investigate closer later, but what I can say is that the group
> nnimap+dtm:ir.announce is not mentioned in ~/News/cache/active, and
> there is no directory that corresponds to it, either.

I now verified that the agent.lib/active file contains a bogus first
number for the groups in question -- 3072 was used for two groups
even though the real number was different (from 3072 and different
for each group).

No idea how that got there, though.  Hm.
-- 
This line is not blank.