Scheduler wildcard for task name no longer executes scheduled tasks
See original GitHub issueExpected behaviour:
'*'
(wildcard) to execute all defined tasks.
Actual behaviour:
'*'
(wildcard) schedule does not execute any tasks.
Steps to reproduce:
Use '*'
(wildcard) for the key name for the scheduled task, instead of an explicit key name of the task.
Config:
schedules:
- tasks: '*'
interval:
minutes: 1
tasks:
media-site:
template: media
discover:
what:
- next_series_episodes: yes
from:
- site: key
templates:
media:
download: /incoming
transmission:
host: localhost
port: 9092
series:
1080p+ !dolbyvision:
- Linux Media
set:
proper: 1 day
label: TV
path: /media/{{series_name}}/{{series_name}} - Season {{series_season}}
content_filter:
require_all:
- '*.mkv'
regexp:
reject:
- spanish
- german
web_server: yes
Log:
With the "*"
wildcard defined, no tasks are run:
2022-02-21 07:17:24 INFO scheduler Starting scheduler
2022-02-21 07:17:24 INFO apscheduler.scheduler Scheduler started
2022-02-21 07:17:24 INFO apscheduler.scheduler Added job "*" to job store "default"
2022-02-21 07:17:24 INFO apscheduler.scheduler Removed job 75f0548cf663cf388c4135157afb88a363701d17
2022-02-21 07:17:24 INFO apscheduler.scheduler Resumed scheduler job processing
2022-02-21 07:17:24 DEBUG apscheduler.scheduler Looking for jobs to run
2022-02-21 07:17:24 DEBUG apscheduler.scheduler Next wakeup is due at 2022-02-21 07:18:24.723283-08:00 (in 59.921033 seconds)
2022-02-21 07:18:24 DEBUG apscheduler.scheduler Looking for jobs to run
2022-02-21 07:18:24 INFO apscheduler.executors.default Running job "* (trigger: interval[0:01:00], next run at: 2022-02-21 07:18:24 PST)" (scheduled at 2022-02-21 07:18:24.723283-08:00)
2022-02-21 07:18:24 DEBUG scheduler executing tasks: ['*']
2022-02-21 07:18:24 DEBUG scheduler all tasks in schedule finished executing
2022-02-21 07:18:24 INFO apscheduler.executors.default Job "* (trigger: interval[0:01:00], next run at: 2022-02-21 07:19:24 PST)" executed successfully
2022-02-21 07:18:24 DEBUG apscheduler.scheduler Next wakeup is due at 2022-02-21 07:19:24.723283-08:00 (in 59.996177 seconds)
Additional information:
- FlexGet version: 3.3.0
- Python version: 3.8.10
- Installation method: pip
- Using daemon (yes/no): yes
- OS and version: Ubuntu 20.04.3 amd64
- Link to crash log: N/A
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:20 (11 by maintainers)
Top Results From Across the Web
Stop-ScheduledTask - Microsoft Learn
Specifies an array of one or more paths for scheduled tasks in Task Scheduler namespace. You can use "*" for a wildcard character...
Read more >Selectively deleting system scheduled tasks - Super User
If you want wildcard (*) to be used in your selection of tasks to delete, try using this simple batch command ...
Read more >PowerShell Start-ScheduledTasks with Wildcard Folder
Run, how can I make Powershell start-scheduledTask run each of those scheduled tasks? I tried. Start-ScheduledTask -TaskName '\Microsoft\*\Run'.
Read more >Displaying, running, and stopping scheduled tasks ... - 4sysops
If you run the cmdlet without parameters, it displays all available tasks with their properties TaskPath, TaskName, and State.
Read more >JAMS 7.X User Guide
Define the Job Source, Schedule, Properties, Parameters, Documentation, ... Configures a Recovery Job to run if the given Job completion does not exceed....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Added a test for this as well 5c834dcdde3abe210fb6ed320d3176dfaf36305e EDIT: Well, not exactly a test for this issue, but a test to make sure manual plugin still works when working around this issue.
This is the way I mean.