Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cannot install with the latest Kue #1

Closed
deckchairhq opened this issue May 18, 2015 · 3 comments
Closed

Cannot install with the latest Kue #1

deckchairhq opened this issue May 18, 2015 · 3 comments

Comments

@deckchairhq
Copy link

Looks a great library, though am yet to try it...

The peer dependencies prevent me using the latest stable Kue:

$ npm install --save kue-scheduler
npm WARN peerDependencies The peer dependency kue@^0.8.12 included from kue-scheduler will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "--save" "kue-scheduler"
npm ERR! node v0.10.32
npm ERR! npm  v2.10.0
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package kue does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer kue-scheduler@0.1.0 wants kue@^0.8.12

I'm currently running "kue": "^0.9.3" and have the latest version of NPM.
@lykmapipo
Copy link
Owner

@thinkgareth

Am on it.

@lykmapipo
Copy link
Owner

@thinkgareth

I have upgrade the to kue v0.9.3.

You may check kue-scheduler v0.1.1 in npm.

Hope it helps.

@skolesnyk
Copy link

Doesn't work with me — I have kue^10.x.

npm WARN EPEERINVALID kue-scheduler@0.4.2 requires a peer of kue@^0.9.6 but none was installed.

lykmapipo pushed a commit that referenced this issue Apr 4, 2019
@ggutenberg
Bind this to done on error (#1)
ef5cb31 
Fixes

```
TypeError: Cannot read property 'emit' of undefined
```

When `restore: true` in the `createQueue()` options object.

This was happening when an error was being passed, as the binding wasn't occuring in that instance.  When I was able to output the error that was occurring, it was:

```
Error: All keys in the pipeline should belong to the same slot
    at Pipeline.exec (/data/node_modules/ioredis/lib/pipeline.js:235:21)
    at Pipeline.pipeline.exec (/data/node_modules/ioredis/lib/transaction.js:34:26)
    at Queue.<anonymous> (/data/node_modules/kue-scheduler/index.js:1428:14)
From previous event:
    at new Pipeline (/data/node_modules/ioredis/lib/pipeline.js:30:18)
    at Cluster.redis.multi (/data/node_modules/ioredis/lib/transaction.js:24:20)
    at Queue.<anonymous> (/data/node_modules/kue-scheduler/index.js:1420:32)
    at runCallback (timers.js:800:20)
    at tryOnImmediate (timers.js:762:5)
    at processImmediate [as _immediateCallback] (timers.js:733:5)
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@deckchairhq @skolesnyk @lykmapipo