-
Notifications
You must be signed in to change notification settings - Fork 24
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
Question: Is it possible to target a specific job to stop rather than to stop the whole scheduler? #12
Comments
@jenseneducation-mattias-von-vogelsang There is a |
Sounds promising. However, ideally I want to be able to terminate the job from the tasks error handler. For example via scheduler.stop('job1'). |
E. g.:
It is not possible to stop job from the task, by design, because task is a child of job, and as such is not aware of its existence. |
Thank you kindly for your example. Unfortunately It would not help me in my use case. I would like that very much, it would fit my specific use case perfectly. Thank you! |
will release a new version later tonight |
Thank you kindly for your implementation. I'll try it out tomorrow. Closing this. |
@jenseneducation-mattias-von-vogelsang Just published 1.2.0 with the stopping/starting functionality. |
@kibertoad Awesome. I just got home, I'll implement it in my code. |
@kibertoad I tried to push a branch for a PR on fastify-schedule to bump toad-scheduler to 1.2 but got a 403. Could you bump it or give me temporary write access to push the branch? |
@jenseneducation-mattias-von-vogelsang Isn't usual GitHub flow to fork a repository and then create a PR from that fork? Also since fastify-schedule doesn't come with package-lock, I believe updating locally should be sufficient. |
Ah! My bad, I'm new to "contributing" to open source. |
New to toad-scheduler. Is there a way to target a specific job, for termination? scheduler.stop() seems to end all running jobs.
The text was updated successfully, but these errors were encountered: