flood
flood copied to clipboard
0 matches for every rss feed
I cannot get rss feeds to work. I get 0 matches for whatever feed I add. I can open the feed link and see that it works. I have tried for example:
https://www.archlinux.org/feeds/releases/
are there any logs anywhere I can check to see why flood cant seem to parse the rss feeds?
What regex are you using in the Match field? If its empty it'll never match anything since it has nothing to check for - see https://github.com/jfurrow/flood/issues/319#issuecomment-296731393
I thought the ”0 matches” in the rss feed entry meant it couldnt find anything at all in the feed. After adding a download rule with regex . *10.* i still get no matches. Also, how can i make the match case insensitive? I have tried /. *TEXT. */gi, but I don't seem to get any matches for that either. Am I supposed to write out the slashes like /REGEX/g?
Okay so I dug through the source code to find that the regexp match is hard coded as global and case insensitive. Does it say somewhere what format you expect for different user input? If there is I haven't found it and if there isn't, you should really add it.
@jfurrow We need to add in the documentation that regex are global and case insensitive. And maybe add maybe add a note tell this in the rss feed box.
I have found adding RSS filters to be very inconsistent. It will occasionally pick things up and add them but most of the time it does not. What I think is going on is that the first time I add a particular feed it picks it up if I do the [\S\s*] filter; but if I remove the filter or feed, then attempt to re-add it nothing is found.
I've tried this with the archlinux feed (https://www.archlinux.org/feeds/releases/) and a game feed (http://patchserver.shroudoftheavatar.com/sotalive/torrents/SotATorrentFeed.xml). The game feed is interesting because I can never get it to recognize all torrents. I was successful one time in getting it to recognize about 60 of them. Either way, it's very inconsistent and unusable on my end as all of my feeds are giving 0 results as of now.
Getting 0 matches even if I force a match with my own URL hosted by me... I can see it doing the GET but nothing else.
Worked with just that.
Is /Debian.*amd64.*/i wrong and I should remove the slashes so it's Debian.*amd64.*?
[[1-9][0-9]?.\d*\ GB] test "Cold War 2018 1080p BluRay DTS x264-HDS[1.93 GB]" not work.

@henjue try to add .* at the beginning of the regexp
The problem is that no matter match or not, it always show 0 matches. I use a proper regex and flood can load torrents as expected,
@xiayyu Show what you're using exactly and I'll tell you if it's correct.
@xiayyu Show what you're using exactly and I'll tell you if it's correct.
number of matches refreshed but I have no idea how long it takes. It did loading rss torrent immediately but keep showing 0 match for a while. So it's not an acute bug.
I'm using git commit version of 912f61abfb66997b89bcf405023772d430ff349d and nodejs installed by nvm the latest lts version (v10.16.0)