On Mon, Mar 17, 2008 at 9:37 PM, Eddy Petrișor <[EMAIL PROTECTED]> wrote:
> Luis Rodrigo Gallardo Cruz wrote:
>
>
> > On Mon, Mar 17, 2008 at 09:48:40PM +0200, Eddy Petrișor wrote:
>  >>>> Lars Lindner wrote:
>  >>> Nonetheless I identified the problem. You do massively mark posts
>  >>> as important (flagged). Which is not forbidden, but was totally
>  >>> unexpected by me when I implemented the merging algorithm.
>  >> Heh :-) . I usually do that so I can come back to them at any time I want
>  >> to do read about the subject of the post. Is a way of archiving for me
>  >> (since I saw is he only way to make liferea keep those posts from being
>  >> lost into nothingness).
>  >>
>  >>> Flagged items do have the property of never being dropped from
>  >> Which is good :-), from my PoV.
>  >>
>  >>> cache, but at the same moment we have a cache limit that the merging
>  >>> algorithm has to cope with. And the current calculation is simple: if the
>  >>> cache limit is 100 (like in your case and per default) and there are 100
>  >>> (or more) flagged items that must never be dropped, then there is just
>  >>> no room to add new items.
>  >> kaboom :-)
>  >>
>  >>> As a temporary workaround you should increase the cache limit for
>  >>> all affected feeds (like the Debian Planet feed).
>  >> I have, but it seems it already "lost" some of the items of the day...
>  >> I'll probably change the limit first, then upgrade once more to the new
>  >> format ;-) .
>  >
>  > If this works for you, please let me know. I'll then downgrade this
>  > report's severity but leave it open as a hint for others.
>
>  Yes, it does, but why hide/bury it?
>
>  Probably Lars will provide a fix soon and the problem will still be visible 
> on an Etch->Lenny
>  upgrade, if missed. I'd say there isn't a need for a severity downgrade, 
> especially since the bug
>  "looks" like is unreproducible at a first glance.

I fixed this in SVN with this revision:

http://liferea.svn.sourceforge.net/viewvc/liferea?view=rev&revision=3766

Solution will be released upstream around next weekend with 1.4.15.

I've tested the change for effectiveness with the cache files
you provided some mails ago. I'll monitor it for stability some
more days... But I think the change is not very intrusive, so
it propably will be ok.

Regards,
Lars

Reply via email to