Closed chrisbgp closed 11 years ago
Switching to mysql did not work either and gives me this error:
Exception _mysql_exceptions.ProgrammingError: ProgrammingError('closing a closed connection',) in <bound method SessionCache.__del__ of <coldsweat.session.SessionCache object at 0x2379110>> ignored
´´´
Syncing does not work automatically. Updating via refresh_feeds.py does work tho.
Indeed, that's the way it works. You should use cron or something similar to schedule feed refresh.
The exceptions you posted seem related to the new session code, which unfortunately is still largely untested. Now that I think about it: I should activate session management only for webviews and not for Fever API. I'll look into it this week-end.
Thanks for testing mysql, I didn't pay too much attention to it.
Ah ok I thought syncing happened automatically inside the app. Updating via cron is fine for me.
Thanks for the help and making your project open source!
Ah ok I thought syncing happened automatically inside the app. Updating via cron is fine for me.
It makes sense for the client (Reeder) but refresh 100+ feeds takes some time (minutes) and so it isn't clear how this would affect the whole process. Does the client wait for it? It isn't documented in the Fever API, but I've found out how a "server refresh" is triggered: https://github.com/passiomatic/coldsweat/wiki#force-a-server-feed-refresh
So at least for now it's a no-no. :)
Yes that is true. Especially on a Raspberry Pi ;-)
Otherwise it works great so far!
sqlite works now after your commit. I think this can be closed.
Not sure what was causing your first sqlite error, I reviewed the session code refactored the connect/close logic. If it happens again please reopen the ticket.
Syncing does not work automatically. Updating via refresh_feeds.py does work tho.
Have not tried mysql yet...