-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Recheck all in ¨tag-name"' doesn't enqueue PAUSED watches #2934
Comments
That's correct, paused watches shouldnt be re-queued. ? |
Hm, why? By pressing the button the user explicitly asked to re-check them. And, as button says, "all watches in tag-name". I would argue the expected behaviour is to check all of them as a response to a manual action. (I am the example of such a confused user. I even filled the first report because had no clue that the button only applies to some watches) |
The way I see it, there are several way to deal with the issue:
|
I remember a little while ago someone filed an issue for the exact opposite, that paused watches were being queued.. I dont want to change that, sorry
No, people could have many watches across different "paged" lists, like 50 per page but you have 300 watches
To what exactly?
No sorry, i think it does what it does |
|
Describe the bug
Here is a CORRECTED report of the closed issue #2932
The UI has a button called 'Recheck all in ¨_tag-name_"' under the list of watches assigned to a tag. Pressing it doesn't enqueue paused watches for re-checking. The appearing notification always says "0 watches queued for rechecking." Non-paused watches are enqueued as expected.
Version
0.49.0
How did you install?
Docker
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The text was updated successfully, but these errors were encountered: