All Versions
92
Latest Version
Avg Release Cycle
40 days
Latest Release
-

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.