There's a new bug regarding PR #116 , that causes a bug on R0 jobs on starting kala after the supposing start time has passed. How to reproduce:
Start kala: go run main.go run --jobDB=redis --jobDBAddress=127.0.0.1:6379
Scheduling a kala job with no repetitions (R0), and so without the interval between repetitions specified:
curl http://127.0.0.1:8000/api/v1/job/ -d '{"command": "date > ~/Desktop/test_kala", "name": "test_job_stop", "schedule": "R0/2016-05-09T16:40:40+01:00/"}'
Stopping kala
Waiting for the starting time has passed
Starting kala go run main.go run --jobDB=redis --jobDBAddress=127.0.0.1:6379
There's a new bug regarding PR #116 , that causes a bug on R0 jobs on starting kala after the supposing start time has passed. How to reproduce:
go run main.go run --jobDB=redis --jobDBAddress=127.0.0.1:6379
curl http://127.0.0.1:8000/api/v1/job/ -d '{"command": "date > ~/Desktop/test_kala", "name": "test_job_stop", "schedule": "R0/2016-05-09T16:40:40+01:00/"}'
go run main.go run --jobDB=redis --jobDBAddress=127.0.0.1:6379