Closed leikoilja closed 3 years ago
Ops, sorry, just realized it's the problem of how the 3rd party package is implemented that I am using for cronjob.
My solution is open PR in the 3rd party package to specify task_command="/usr/local/bin/task"
when initializing TaskWarrior
client
I'm getting an error when running a cronjob that is supposed to sync tasks. In short, the error traceback boils down to the place to the
backend.py
fileTaskWarrior
client:running the
subprocess.Popen
whereself._get_task_command()
is returningtask
The weird part is that when I run
task --version
from my user it returns2.5.1
, but using a job throughcrontab -e
(these jobs should run using the same user) it ends up in the error.