RSS rules ignore download path changes

[ngseer]

Type: Bug Report

• [x] Try to follow the update procedure described in the README and try again before opening this issue.
• [x] Please check the F.A.Q..
• [x] Please check the Troubleshooting wiki section.

Your Environment

• Version used:
  • Commit ID 184edaa
• Environment name and version:
  • Node.js version v10.15.2
  • npm version 5.8.0
  • Web browser Google Chrome Version 75.0.3770.100 (Official Build) (64-bit)
• Operating System and version:
  • Ubuntu 19.04 w/ Linux 5.0.0 kernel

Summary

After editing download path at the existing RSS rule Flood still downloads new torrents to the old path.

Expected Behavior

Flood downloads new torrents to the new path.

Steps to Reproduce

1. Add any frequently updated RSS feed (I was using nyaa.si global feed to reproduce it quickly but other feeds are affected too).
2. Add a download rule. Regex pattern doesn't seem to matter so the easiest way is to use .* for matching all torrents.
3. Wait for a new torrent added from the feed. Check that it's going to be downloaded to the specified path.
4. Change download path for the download rule added at the step 2.
5. Wait for another torrent. See that it's still going to be downloaded to the old path instead of the new one.

[ngseer]

Update: I've just noticed that Flood keeps adding torrents from the feed even after the rule was removed. It may be related to this bug but I can create another issue if necessary.

[noraj]

Is the change taken into account after restarting flood process ?

[ngseer]

@noraj yes, it changes after restart.

[mattgorecki]

I ran into this same issue. Also, whatever the state of the Start On Load checkbox is at the time of the rule creation, is what it sticks with until the Flood process is restarted. In other words, it appears that edits to the Download Rule don't take affect on submission.