Feeder: a RSS-plugin for deluge >= 1.1

[typhoe]

Hi,

I'm using feeder v0.3 and deluge 1.1.4 (ppa) on a ubuntu intrepid server.

I don't use the gtk ui.

Feeder appears in the webui.
I have configured a rss feed, a filter (which display a "matches").
The torrent url link of the "matches" if inserted "manually" in deluge works perfectly.

My problem is that feeder doesn't seem to be "running" and I can't find a log helping me to find why...

Deluge log (deluged.log) stays empty.

Not sure it's an issue, but I'm running a "french" ubuntu install. I say that because deluge detects my language and use this language when it displays the web ui.
And when I want to set a new filter, the word "Illimité" (unlimited in english) is not recognized.
So, I have to replace it by "-1" to add a filter each time for example.

Is there a way to check if feeder is running? to enable a debug mode?

Thank you,
Typhoe

[danii]

to enable logging check http://dev.deluge-torrent.org/wiki/Faq# ... ingenabled

[feffe]

@typhone

I know about the "unlimited" vs -1 issue. I'll look into it at some point. Otherwise, as danii said, try to activate debug logging...

Just to let people know: I do intend to continue develop this plugin at some point. It will probably take a while before I can do anything due to work/school/other-stuff-that-needs-to-be-done.

[typhoe]

Hi,

thank you for pointing me to the right url, danii (I should have read the wiki more carefully... sorry :/).

I have joined the debug log of a "fresh" session.
EDIT: Can't manage to upload an attachment??? see : http://pastebin.com/f5f959e7e

Feeder has a rss feed configured and 2 filters (one with no match and another with 4 matches).

I only start the core (deluged -L debug), wait a few minutes (doesn't matter if I wait for hours, there's no change), then kill the core (killall deluged).

So feeder seems to detect the matches, and "add" them, but the downloads don't really start (see before 16:06)

At 16:09, I issue the core shutdown, and then the "alertmanager" seems to detect my 4 downloads (but none was in progress before.... ?) and to change their states to "downloading" but the core is shutting down....

So, any idea? :p

Thank you,
Typhoe

[feffe]

Have you changed any of the default settings for the filter? like any speed settings? I think the speed setting was broken for no apparent reason...

[typhoe]

Yes and no:

I had to replace all the "illimited" ("Illimité" in french) values (the 4 ones) by "-1" to be able to save/create the filter.

If I only try to set a regex and save, I get an error:

Traceback (most recent call last):
File "/var/lib/python-support/python2.5/deluge/ui/webui/lib/webpy022/wsgiserver/__init__.py", line 628, in communicate
req.respond()
File "/var/lib/python-support/python2.5/deluge/ui/webui/lib/webpy022/wsgiserver/__init__.py", line 361, in respond
response = self.wsgi_app(self.environ, self.start_response)
File "/var/lib/python-support/python2.5/deluge/ui/webui/lib/webpy022/webapi.py", line 314, in wsgifunc
print >> debug, traceback.format_exc()
File "/var/lib/python-support/python2.5/deluge/ui/webui/lib/webpy022/webapi.py", line 170, in _debugwrite
out.write(x)
IOError: [Errno 5] Input/output error

It doesn't happen when I change the 4 "Illimited" to "-1" in the speed section.

[feffe]

So the speed setting is really broken I'll put this on the fix-list.

[typhoe]

Thank you very much!

I'll be looking for the next release of feeder

[dack]

I've made a slight modification to version 0.3 that adds a "history" system. This prevents adding a given torrent more than once. The history is not saved to disk, so torrents will be readded if you shut down deluged. The last 50 URLs added to the queue are remembered, which should be plenty for most uses.

I haven't done very thorough testing (it's only about 5 lines of code) and it's an "unofficial" version, but I thought some might find it useful. You can at least delete the "junk" entries from your queue and not have them keep showing up.

A better version of this should probably:
- allow the user to change the number of history items remembered
- save history to disk
- allow the user to enable/disable history

[feffe]

That's nice dack, could you send me a patch? (deluge <at> winterbird.org)

otherwise my plan for 0.4 looks like this:
* Implement per-feed activation of filters
* Link rewriting
* remove *any* configuration in the gtk-ui
* fix speed settings (since I just can't understand how this is supposed to work I'll probably just remove the speed settings for now)