igloo-be / cron-cluster Goto Github PK

Test timer must be faked for faster test running
using sinon.js: http://sinonjs.org/

{
    setUp: function () {
        this.clock = sinon.useFakeTimers();
    },

    tearDown: function () {
        this.clock.restore();
    },

    "test should animate element over 500ms" : function(){
        var el = jQuery("<div></div>");
        el.appendTo(document.body);

        el.animate({ height: "200px", width: "200px" });
        this.clock.tick(510);

        assertEquals("200px", el.css("height"));
        assertEquals("200px", el.css("width"));
    }
}

Hi: @Natsuke

I'm using latest redis version, when pass redis client to cron-cluster I got this

Err wrong number of arguments for set command.

This my code

var client = require("redis").createClient();
var CronJob = require('cron-cluster')(client).CronJob

var job = new CronJob('* * * * * *', function () {
console.log("here timer");
})
job.start()

May someone help me with that. tks

I want write gui for management list cron
Feature:

• List cron
• add cron
• remove cron
• update cron (option)

There is a bug when you are using an object as first parameter of the CronJob instance, like this:

`js
var redis = require('redis').createClient()
var CronJob = require('cron-cluster')(redis).CronJob

function doCron () {
var job = new CronJob({
cronTime: '* * * * * *',
onTick: function () {
// Do some stuff here
}
})
job.start()
}
`

this will create an instance of our application which is not synchronized with the other ones in the cluster.

Bugfix is available here: #5

First of all, thanks for your work on this package, cool that something like this exists! 🙌

Considering that this library hasn't received any new commits or publishes in the last 4 years, would you suggest a modern alternative?

Looking at comparison of competing libraries on npm trends, some more low-level alternatives like async-mutex, async-lock and mutexify are suggested.

This seems to be a similar approach to this Stack Overflow answer

Would you suggest using one of these alternatives? Or some different approach?

Per lodash/lodash#3744 (comment), the modularized lodash packages are deprecated. Let's use lodash/wrap instead of lodash.wrap!