Vaughn Iverson

And just a final note, when you ran `meteor test-packages ./` on your local clone of the job-collection repo, meteor successfully *built and executed* job-collection on your platform. So, the...

@lmachens I'm blocked by my inability to reproduce the problem. I'm not setup to support Windows. Based on what we know, I'm about 85% sure it's a Meteor issue, but...

Somebody should file an issue with the Meteor project on this. Since I can't reproduce it, It can't be me.

Two published versions on Atmosphere each have this same problem installing on Windows (1.5.0 and 1.5.1). Multiple people have now verified that these versions run fine on Windows if they...

Hi, just so you know, I'm about to drop off the internet for almost a month, so I won't be able to look into this until around June 20th. Sorry...

@sdarnell I don't think these are related. JobCollection versions 1.4.x and 1.5.x are identical w.r.t. the git submodule and its dev dependencies. 1.4.x installs fine from Atmosphere on Windows (under...

`"Running job not found"` is logged to the console when a worker tries to run `job.done()` or `job.fail()` on a job that is no longer considered to be in the...

Hi, thanks for your suggestion. To be honest this package has settled into a kind of "maintenance mode" where I'm not implementing any new major features. Mostly because I'm not...

If you want very low latency, I recommend using the approach outlined here (instead of polling): https://github.com/vsivsi/meteor-job-collection#qtrigger---anywhere That will take care of the "worker" side. On the server side, you...

@mitar, thanks for this, but is this sufficient to handle all of the cases with repeating jobs etc?