Old tag items are missing if restarting daemon session (former: default.keep_unread seems to be ignored with 0.9) about canto-next HOT 20 CLOSED

The option is "defaults.keep_unread" (note the s on defaults) and can be queried with ":set defaults.keep_unread" or set by giving that an argument (True/False). The option should still be honored, and if you run the daemon with -v, it should print "Keeping unread item: [id]" to the log if the item would've been discarded otherwise.

I'll check it out.

from canto-next.

Seems to be working here... did you have the right option set?

from canto-next.

"defaults": {
"global_transform": "filter_read",
"keep": "2000",
"keep_unread": true,
"rate": 100
}

I'm waiting for the result with verbose daemon.

But since I upgraded from 0.8.x to 0.9 I lost everything that was kept and since then I only have the stuff that's available from the feed. Like 40 of the most recent posts. Stuff that's discarded from the feed is vanishing in canto (dunno how to describe that properly)

Edit: For example techdirt.com (http://feeds.feedburner.com/techdirt/feed). They keep 25 posts. I just have those 25, but didn't read an article for some days

from canto-next.

Hrm.. reading through the log. It clearly says keeping unread items

But I stumpled upon keep_time messages. Does that mean, the keep is setting a time after which they get discarded? I thought this is setting the number of items kept (Dunno why I set this and when. Maybe there were a problem I thought this would fix it and forgot it after that)

Curious is still the fact that I just have the most recent articles from the feed

from canto-next.

"keep" hasn't existed since sometime in 0.8.x I believe, it was replaced with "keep_time" which specifies the number of seconds between an item disappearing from the feed and the daemon being allowed to get rid of it. It defaults to 86400, so items will be kept for a full day after they're no longer in the feed.

from canto-next.

keep_time came with 0.9? Or existed previously? Unread stuff was kept forever with 0.8 (and thats what I want).

Ok, so removing the keep option. And replacing it with keep_time. Any limit for setting the number? Or is there a valid replacement for "keep forever"?

from canto-next.

keep was switched to keep_time right before the 0.8.2 release of the daemon.

keep_unread takes priority over keep_time, so unread items will be kept forever. For read items, keep_time has no upper limit but there's no setting for "forever"

from canto-next.

And now we're back at the beginning :D I'm at a loss now.

Could my setup be a problem? The daemons runs locally and as such just when this machine is running.
If the daemon fires up and do whatever it does and checks if the feed-item is overdue (keep_time) but ignoring keep_unread then?

Anyway. I will look again at it. When this problem is appearing. And what's happening if the daemon is running some time.
I noticed this just with a new daemon session everytime. Dunno about longtime runs and such.

from canto-next.

The same mechanism is used to populate feeds from the net as well as disk so initialization shouldn't be a problem.

Yeah, let me know if you can get a log when you see the behavior. canto-curses also takes -v and might be helpful as well.

from canto-next.

Also, to be clear, they disappear from canto-curses, but they don't return if you restart c-c or trigger an update (\ or F5) or refresh (C-r)?

from canto-next.

No, refreshing and updating and restarting doesn't help in that case. I still just see the feeds that are available from the feed, no more when there should be more.

from canto-next.

Hmm. Found entries in the log where it says, that it's keeping unread item x (example from july 2014 (clearly over keep_time)), but it isn't shown in curses.
Could be the filter_read the culprit?

from canto-next.

That could be a lot of different things. Could you post your logs, or email them to me ([email protected])?

from canto-next.

I emailed them

from canto-next.

Next try in emailing it. Came back. SOmething went wrong with copy and paste from FF to TB...

from canto-next.

Ok and now some observations.
Starting daemon, fetching stuff. Every new feed-item will be appended. This persists between canto-curses sessions. (example one went from 40 to 41 (and they hold 40 items in the feed)). Quited curses, started again and still 41
canto-remote kill and started a new daemon session. Started curses and the items were again 40 (40 items from the feed)

from canto-next.

Ok, I will upload those to gist.
G-Mail rejects me :P
550-5.7.1 [2607:f2e0:f:4d5::2 12] Our system has detected that this message
550-5.7.1 is likely unsolicited mail. To reduce the amount of spam sent to
550-5.7.1 Gmail, this message has been blocked.

Daemon log https://gist.github.com/Narrat/05795145c3cc1f9c67ea/raw/daemon%20log
Curses log https://gist.github.com/Narrat/05795145c3cc1f9c67ea#file-curses-log

from canto-next.

Can you try this daemon patch?

https://gist.github.com/themoken/63f7eed82add3a018972

from canto-next.

Actually fairly certain that patch is the fix (it resurrected some items here), so it's also in git now. Let me know if it works.

from canto-next.

Yes, it's working again.

Thanks for the fix

from canto-next.