Daemon never deletes any of the items about canto-next HOT 16 CLOSED

Hey, are you running 0.8.x or are you running git? I've fixed some pretty nasty bugs with the daemon in the past few weeks.

Also, bugs like this running canto-daemon with -v and pastebinning a copy of ~/.canto-ng/daemon-log would be helpful.

from canto-next.

I'm running 0.8.* (arch linux aur package). I'll try using git version now and send you daemon-log file if this happens again.

This is how it looks after I do "canto-curses -a 192.168.100.11 -p 7070", connect to RPI, reading some news, unreading these news and quitting the client (after installing git version everything works faster): https://dl.dropboxusercontent.com/u/70091792/daemon-log
And my "feeds" file is currently 31M size.

from canto-next.

After switching to git version daemon just doesn't save anything I read at all. I just marked as read ALL items 3 times, then quit canto-curses and open it again. All the same items appeared plus some more (which were loaded just now). So I'm back to 0.8* version for now because I need rss working
I updated the link to daemon-log file (which I posted in the previous comment) so that it is current log.

from canto-next.

When you updated the daemon, did you also update curses? Git might be a bit rough, but it's not as broken as that - at least when used with the git client as well...

from canto-next.

Yes, of course I've updated both client and daemon. But I did not erase any content (like "feeds" file) from daemon-side directory.
Anyway I'll try to migrate to git version again when I find some more time, probably somewhere near next week.

from canto-next.

Deleting it shouldn't be necessary. Anyway, are you sure that's the entire daemon-log? It's only ten seconds of running and I don't see any socket traffic...

from canto-next.

Yes, that's all (maybe client was never connected to the daemon, that's probably why none of read items were saved). I just updated daemon log which is already running like 16 hours (with canto 0.8.*), you can see it here https://dl.dropboxusercontent.com/u/70091792/daemon-log

from canto-next.

I've figured out that canto-next-git version of daemon won't even start, it exits with "Can't convert 'NoneType' object to str implicitly" error. I start it like this: "canto-daemon -v -p 7070", and daemon-log says nothing but the same: http://dl.dropbox.com/u/70091792/Screenshots/September/09-194733.png

And if I start it just like "canto-daemon", then it just silently exits with "Unexpected end of file" error of gdbm in daemon-log: http://dl.dropbox.com/u/70091792/Screenshots/September/09-194934.png

UPD: I have deleted all contents except "conf" file from .canto-ng folder and it seems to work, in daemon-log just canto-fetch repeatedly tells "no canto-update in feed URL: ~". But then if I try to run it with "-v -p 7070" options - it exits with
19:54:15 : CANTO-DAEMON -> Received INT
19:54:15 : CANTO-DAEMON -> Interrupted. Exiting.
19:54:15 : CANTO-DAEMON -> Exiting cleanly.

If I then remove all contents except "conf" file again and run it with "-v -p 7070" options - it crashes again but this time with
19:56:24 : CANTO-DAEMON -> Error: Can't convert 'NoneType' object to str implicitly

UPD2: Well, I guess I've just fixed the problem: If I run it with "-a 127.0.0.1 -p 7070" all works fine. So old version allowed user to just select port to listen on and if "-a" was not presented, canto-curses were to select "127.0.0.1" automatically. But git version doesn't do so and if you try to use -p without -a, you'll get NoneType error.

from canto-next.

Ah, ok, good catch, I'll make it assume loopback.

from canto-next.

I made the commit to assume loopback.

Anyway, has the initial issue been resolved in git?

from canto-next.

Also, sometimes when you mark some news as "read" and immediately exit canto-curses, daemon doesn't mark them and when you run canto-curses again - they appearing again (maybe an issue with my network). And I can't connect over lan now (seems strange, because I've managed to do it on 0.8*) - only ssh -L way works.

Anyway, there's daemon-log file for a couple of minutes of testing new canto: https://dl.dropboxusercontent.com/u/70091792/daemon-log

I don't know if the initial issue has been resolved, I've just started using it ten minutes ago. Hope it is resolved, but gonna test it to be sure.

from canto-next.

Ah, I see what's going on here.

Before the daemon would default the address to "", which isn't loopback it's "All available interfaces" which is probably insecure. I think loopback is a better default.

However, -a "" -p 7070 works here to get that behavior.

from canto-next.

It works perfectly :) My 7070 port is closed so I'm using this method only via LAN at home for simplicity. Although if you'd like to share an alias for forwarding port via ssh and running canto-curses with one command - I would be thankful.

from canto-next.

By the way, is it supposed to be like that when you "read" tags and then try to hide/show whole section?
http://dl.dropbox.com/u/70091792/Screenshots/September/09-220830.png
(should it be another issue?)

from canto-next.

That is another issue, but I'm actually working on it right now

from canto-next.

Should be fixed in git. I'm closing this because the initial issue is dead. If you have any other trouble, feel free to open another, or visit #canto on freenode.

from canto-next.