flood
flood copied to clipboard
New RSS feeds do not work until flood restarted
From what I can tell, new RSS feeds wont start matching any download rules until Flood is restarted.
I.e, when I first setup flood, I had a match [\s\S]
download rule for 4 days without a single match on a feed with daily additions. Restarted flood and everything it missed during the 4 days were added.
I've also recently noticed that RSS feeds also stop working if rtorrent dies for whatever reason (i.e lack of storage) and restarted while flood is running.
Thanks for the bug report, I'll look into this.
This is still an issue, at least on Firefox. I run the latest source from master (where this should be fixed) but it's not working. I have to restart the docker image for the RSS changes to take affect.
E.g. When removing an RSS entry, it still gets downloaded if the docker image is not restarted.
@enoch85 Please provide those:
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used:
+ Version (stable release) `git --no-pager tag`
+ Commit ID (development release) `git --no-pager log -1`
* Environment name and version:
+ Node.js version `node --version`
+ npm version `npm --version`
+ Web browser `name and version`
* Operating System and version:
@noraj I use this in a Docker which is building flood from master: https://github.com/binhex/arch-rtorrentvpn/blob/master/build/root/install.sh#L45 but it's not a Github dir so I can't run the git command. It's the latest from 3 days ago anyway. Regarding the other commands:
[root@9bfa54121632 /]# node --version
v11.4.0
[root@9bfa54121632 flood]# npm --version
6.5.0
Firefox Quantum 64.0 (64-bit) Ubuntu Budgie 18.04.1
I'm not quite on latest (some commit in late summer - accidentally killed the droplet while on vacation so can't start it to get commit hash atm), but #330 did fix this with RSS feeds being active on creation and deleted. Flood hasn't restarted in the past 4 months with several RSS feeds added/removed since then, so potentially a recent regression or an issue effecting the Docker images :disappointed:
Node: 11.6.0 Browser: FF64 OS: Ubuntu 18.04 (Flood instance)
I am not able to reproduce the issue on the latest version of Flood.
Try to upgrade to the latest version of Flood.
If the issue is no longer relevant, feel free to close it.