Skip to content
This repository has been archived by the owner on Jun 8, 2020. It is now read-only.

Make sure config is in scope for kue init #62

Merged
merged 1 commit into from
Dec 6, 2014
Merged

Make sure config is in scope for kue init #62

merged 1 commit into from
Dec 6, 2014

Conversation

md5
Copy link
Contributor

@md5 md5 commented Dec 6, 2014

I was playing around creating a Docker image for Reportr and hit this error:

ReferenceError: config is not defined
    at Object.init (/usr/src/app/lib/queue/kue.js:11:30)
    at /usr/src/app/lib/index.js:22:22
    at _fulfilled (/usr/src/app/node_modules/q/q.js:787:54)
    at self.promiseDispatch.done (/usr/src/app/node_modules/q/q.js:816:30)
    at Promise.promise.promiseDispatch (/usr/src/app/node_modules/q/q.js:749:13)
    at /usr/src/app/node_modules/q/q.js:557:44
    at flush (/usr/src/app/node_modules/q/q.js:108:17)
    at process._tickDomainCallback (node.js:463:13)

This patch made things work.

SamyPesse added a commit that referenced this pull request Dec 6, 2014
Make sure config is in scope for kue init
@SamyPesse SamyPesse merged commit e5cbb5d into Reportr:master Dec 6, 2014
@SamyPesse
Copy link
Member

Thanks 👍 🍻

@md5 md5 deleted the fix-kue-redis-config branch December 6, 2014 23:39
@md5
Copy link
Contributor Author

md5 commented Dec 6, 2014

Sure thing.

I've switched my Dockerfile back to your fork using e5cbb5d. If you want to cut a new tag, I'll switch it to that instead.

@SamyPesse
Copy link
Member

Version is bumped to 3.5.1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants