Hey guys! another quick update from shipping packages: the synced-cron oldie but goodie somehow looked confusing and unmaintained for meteor V3 with a few forks unresolved here and there, so I decided to rebuild something roughly equal from scratch and release it so it works with meteor 3 properly. If anyone has issues with the current previous options of this famous package, maybe have a look into my take and let me know if its working or has missing features!
… lets modernize the ecosystem step by step
4 Likes
Great to see this.
At Quave we use our version with some new features:
# Changelog
## 2.2.1 (2024-12-13)
- Add automatic cleanup of running jobs when the process encounters a fatal error (uncaught exceptions and unhandled rejections). The cleanup consists of marking the job as finished and adding a `terminatedBy` field to the job history collection to indicate how the job was terminated.
- Add tests for the new functionality.
## 2.2.0 (2024-10-07)
BREAKING CHANGE: `allowParallelExecution` is now `false` by default. Before, this package was allowing parallel executions except when the intendedAt was equal. Now, it's not allowing by default any parallel execution. So, if you want to keep the old behavior, in your add function, you should always provide `allowParallelExecution` as true.
- Add `allowParallelExecution` option to `SyncedCron.add`. This option allows to run the same job in parallel.
- Add `timeoutToConsiderRunningForParallelExecution` option to `SyncedCron.add`. This timeout is a number in miliseconds. If the job takes more time than `timeoutToConsiderRunningForParallelExecution` and it's not finished, another instance of the job can be run in parallel.
- Add tests for all the new changes since 2.0.9.
## 2.1.0 (2024-10-07)
- This is actually 2.0.9 but as Meteor 3.0.3 is failing to publish only metadata I bumped the version to 2.1.0.
show original
Feel free to copy them if you like
http://packosphere.com/quave/synced-cron
1 Like
!