-
Notifications
You must be signed in to change notification settings - Fork 625
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
waitForCompletion
not working as expected
#923
Comments
tagging @Zamoca42 who worked on the PR. I'll add your test case as well and see if I can figure out what's going on |
does this test case illustrate the issue you're experiencing? |
Yes, that test asserts an incorrect result. I added a comment below yours: #894 (comment) |
🎉 This issue has been resolved in version 3.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## [3.3.1](kelektiv/node-cron@v3.3.0...v3.3.1) (2024-12-12) ### 🐛 Bug Fixes * correct waitForCompletion behavior ([kelektiv#924](kelektiv#924)) ([f6270f8](kelektiv@f6270f8)), closes [kelektiv#923](kelektiv#923) [kelektiv#923](kelektiv#923) [kelektiv#894](kelektiv#894)
Description
In my testing I can't get
waitForCompletion
to stop another instance of a job running concurrently as expected based on changes made and documented in 3.3.0.Expected Behavior
waitForCompletion
should stop multiple instances running concurrently, as documented.Actual Behavior
Setting
waitForCompletion
true or false doesn't seem to make any difference.Possible Fix
No response
Steps to Reproduce
Output
Expect
Context
I had previously implemented my own solution to stop multiple instances of a job running concurrently. I thought with 3.3.0 I could simplify my code and instead use the new feature provided by
cron
.Your Environment
cron
version: 3.3.0The text was updated successfully, but these errors were encountered: