Skip to content
Commits on Sep 13, 2012
  1. Change timings in the failing test.

    committed Sep 13, 2012
    Appears to be some kind of race condition within the test suite. This
    is just an attempt at seeing whether it is fixed on travis.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  2. Version bump and api.

    committed Sep 13, 2012
    Bump the version and inform the api.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  3. Remove logging when timeout is large.

    committed Sep 13, 2012
    We put a logging message into the code to inform people of when the
    timeout for their cronjob was going to exceed the maxint value that
    setTimeout allows (which would change the timeout to 1). This has since
    been fixed in the code and the logging is no longer necessary.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on Sep 11, 2012
  1. Specify context for onComplete.

    committed Sep 11, 2012
    It seems to be a nice feature that the oncomplete method be allowed to
    have a specific context within which to execute (GH-47).
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on Sep 1, 2012
  1. Submitting bugs/issues.

    committed Sep 1, 2012
Commits on Aug 30, 2012
  1. Artifially bump only cron style times. (GH-43)

    committed Aug 30, 2012
    We were artificially bumping all crontimes by 1 second to ensure that
    the timeout didn't fire on repetitive jobs many times (omg fire
    now...and again, and again and so on...). This was incorrect and
    unexpected behavior for specific date/time values. We now only bump cron
    style date/time values.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  2. Reset the time.

    committed Aug 30, 2012
    It may be nice to be able to reset the time on a cronjob. In order to do
    this we need to assert that the time is a CronTime, assert that the
    existing job has been stopped (assume that the stop function is
    working), and then change the time. We leave it up to the user to
    restart the job.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on Aug 7, 2012
  1. Update README.md

    committed Aug 7, 2012
  2. better links.

    committed Aug 6, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  3. links

    committed Aug 6, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  4. Version Bump and backwards compatibility explanations.

    committed Aug 6, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  5. npm install .

    committed Aug 6, 2012
    Before running the tests or any installation (which runs the tests) we
    want to npm install the dependencies to make sure that the tests can
    run.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on Jul 26, 2012
  1. @danhbear
Commits on Jul 24, 2012
  1. @danhbear
  2. @danhbear
Commits on Jul 4, 2012
  1. Version bump.

    committed Jul 4, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  2. Warn when the max timeout is too large.

    committed Jul 4, 2012
    The max timeout being too high will cause the timeout to fire
    immediately. While this has been fixed, we need to warn people when the
    timeout has been changed by the library. This just lets the developer
    know of the change.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  3. Merge pull request #40 from calmh/fix-long-sleep

    committed Jul 4, 2012
    Correctly handle long sleep times
Commits on Jul 3, 2012
  1. @calmh

    Add test case for long wait

    calmh committed Jul 3, 2012
    When scheduling a job 32 days into the future, we should not get the
    callback within 250 ms.
Commits on Jul 1, 2012
  1. @calmh

    Correctly handle long sleep times

    calmh committed Jul 2, 2012
    Currently the code tries to setTimeout for too long intervals when
    handling for example a monthly job. This commit fixes the wait logic so
    that it doesn't try to sleep longer than the setTimeout maximum of
    2^31-1 milliseconds (24.9 days).
Commits on Jun 25, 2012
  1. Added v0.8.0 support.

    committed Jun 25, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on Jun 8, 2012
  1. Version bump and contributor.

    committed Jun 8, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  2. Merge pull request #37 from baryshev/patch-1

    committed Jun 8, 2012
    Fixed loss of timeZone when the parameters are passed as an object.
Commits on Jun 7, 2012
  1. @baryshev
Commits on May 25, 2012
  1. Version.

    committed May 25, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  2. Build NAOW!

    committed May 25, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  3. Rerun build?

    committed May 25, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  4. Node v0.7.x in travis.

    committed May 25, 2012
    Changes to support the latest node env in Travis.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  5. Merge branch 'master' of https://github.com/toots/node-cron

    committed May 25, 2012
    Conflicts:
    	tests/test-cron.js
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on May 24, 2012
  1. Version bump to 0.3.1

    committed May 24, 2012
    Bump the version to cover the failure of onCompletes.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  2. Fix tests and make sure onComplete runs - GH-35.

    committed May 24, 2012
    onComplete wasn't being called correctly. While it was being passed to
    the onTick calls appropriately it should have been fired when the job
    was explicitly stopped or when the timer ran out, not to be run again.
    This wasn't happening.
    
    Additionally, the tests for onComplete were really bad. They were
    expecting that the onTick fire off the onCompletes. That is...lacking to
    say the least. This has now been fixed as well.
    
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on May 9, 2012
  1. Make sure date values only fire once per GH-34.

    committed May 9, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
  2. Failing test for dates to make sure they fire only once.

    committed May 9, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Commits on Apr 25, 2012
  1. @toots

    Various fixes.

    toots committed Apr 25, 2012
  2. Version bump due to features and bug fixes.

    committed Apr 24, 2012
    Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
Something went wrong with that request. Please try again.