Skip to content
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

fix: don't start job in setTime if it wasn't running #661

Conversation

sheerlox
Copy link
Collaborator

@sheerlox sheerlox commented Apr 14, 2023

I started by wrapping the setTime test cases in a describe, so changes might not be obvious for tests/cron.test.js. Please see the commits detail for better readability.

Fixes #598.

@sheerlox sheerlox changed the title fix: don't start job in setTime if it wasn't running (fix #598) fix: don't start job in setTime if it wasn't running Apr 14, 2023
@sheerlox sheerlox force-pushed the fix-598/setTime-check-job-status-before-starting branch from 91e37b9 to 2f578bc Compare April 16, 2023 12:10
@sheerlox
Copy link
Collaborator Author

rebased against master to resolve conflicts.

@intcreator intcreator merged commit 7e26c23 into kelektiv:master Apr 22, 2023
@intcreator
Copy link
Collaborator

thanks for your work on this, looks good!

@sheerlox sheerlox deleted the fix-598/setTime-check-job-status-before-starting branch May 21, 2023 14:12
@ncb000gt
Copy link
Member

ncb000gt commented Jul 24, 2023

🎉 This PR is included in version 2.3.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@sheerlox sheerlox added the type:bug Bug reports and bug fixes label Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released type:bug Bug reports and bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] setTime() starts the job even if the job was stopped
3 participants