Changelog History
Page 3
-
v2.7.0 Changes
โ ADDED keep alive necessary to keep IronMQ connection open.
๐ Officially only supported on Node.js 4.0 or later.
-
v2.6.0 Changes
July 15, 2015๐ CHANGED tests that schedule with interval now respect start time.
โฑ When scheduling a job to run every 24 hours, it will run at 0:00 starting on the next day.
โฑ When scheduling a job to run every 24 hours from the start time. Previously โ this was not respected in the test suite.
โฑ This allows you to run a job every 24 hours at 5:00 by scheduling with:
{ every: '24h', start: new Date(null, null, null, 5) }
-
v2.5.0 Changes
June 29, 2015โ ADDED
resetSchedule
to help test scheduled jobs. -
v2.4.2 Changes
June 29, 2015๐ FIXED
runOnce
should continue to honor intervals after first run. -
v2.4.1 Changes
June 24, 2015๐ FIXED start time scheduling.
-
v2.4.0 Changes
June 23, 2015๐ CHANGED when testing, you need to advance the clock to run a scheduled job.
For example:
Ironium.scheduleJob('daily', '24h', function(done) { console.log('Run daily job'); }); await Ironium.runOnce(); TimeKeeper.travel(Date.now() + ms('24h')); await Ironium.runOnce(); => Run daily job
-
v2.3.10 Changes
June 22, 2015๐ FIXED sometimes errors during job handling go ignored.
-
v2.3.9 Changes
June 21, 2015๐ FIXED do not swallow processing errors that have the same signature as beanstalkd errors.
-
v2.3.8 Changes
June 21, 2015๐ FIXED round up schedule to next interval.
-
v2.3.7 Changes
๐ FIXED pass jobID to error handler via domain.