{"action":"created","issue":{"url":"https://api.github.com/repos/LewisJEllis/bee-queue/issues/27","labels_url":"https://api.github.com/repos/LewisJEllis/bee-queue/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/LewisJEllis/bee-queue/issues/27/comments","events_url":"https://api.github.com/repos/LewisJEllis/bee-queue/issues/27/events","html_url":"https://github.com/LewisJEllis/bee-queue/issues/27","id":121049073,"number":27,"title":"Error: NOSCRIPT No matching script. Please use EVAL.","user":{"login":"davisford","id":186677,"avatar_url":"https://avatars.githubusercontent.com/u/186677?v=3","gravatar_id":"","url":"https://api.github.com/users/davisford","html_url":"https://github.com/davisford","followers_url":"https://api.github.com/users/davisford/followers","following_url":"https://api.github.com/users/davisford/following{/other_user}","gists_url":"https://api.github.com/users/davisford/gists{/gist_id}","starred_url":"https://api.github.com/users/davisford/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davisford/subscriptions","organizations_url":"https://api.github.com/users/davisford/orgs","repos_url":"https://api.github.com/users/davisford/repos","events_url":"https://api.github.com/users/davisford/events{/privacy}","received_events_url":"https://api.github.com/users/davisford/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-12-08T16:48:19Z","updated_at":"2015-12-08T18:05:32Z","closed_at":null,"body":"I'm opening a new issue - related to #24 b/c 24 is closed, but unresolved, as far as I can tell.\r\n\r\nI'm trying to migrate from kue to bee-queue, and when I start up the app, it throws this error:\r\n\r\n```\r\nError: NOSCRIPT No matching script. Please use EVAL.\r\n    at ReplyParser.<anonymous> (/Users/davis/git/warehouse-web/node_modules/bee-queue/node_modules/redis/index.js:320:31)\r\n    at ReplyParser.emit (events.js:107:17)\r\n    at ReplyParser.send_error (/Users/davis/git/warehouse-web/node_modules/bee-queue/node_modules/redis/lib/parser/javascript.js:298:10)\r\n    at ReplyParser.execute (/Users/davis/git/warehouse-web/node_modules/bee-queue/node_modules/redis/lib/parser/javascript.js:183:22)\r\n    at RedisClient.on_data (/Users/davis/git/warehouse-web/node_modules/bee-queue/node_modules/redis/index.js:550:27)\r\n    at Socket.<anonymous> (/Users/davis/git/warehouse-web/node_modules/bee-queue/node_modules/redis/index.js:105:14)\r\n    at Socket.emit (events.js:107:17)\r\n    at readableAddChunk (_stream_readable.js:163:16)\r\n    at Socket.Readable.push (_stream_readable.js:126:10)\r\n    at TCP.onread (net.js:538:20) +2ms\r\n```\r\n\r\n...which I understand to mean Redis is saying the Lua scripts are not cached, so they'll need to be `EVAL`'d instead.  This should be true since I'm just trying bee-queue for the first time.\r\n\r\nHowever, I also pulled the proposed fix from #24 [commit here](https://github.com/mllongze/bee-queue/commit/8cefcb25b27c23840ca668578d3ae4bcdf4ebcd3)\r\n\r\n```\r\n$npm ls --depth=0 | grep bee\r\nnpm info it worked if it ends with ok\r\nnpm info using npm@3.4.1\r\nnpm info using node@v0.12.2\r\n├── bee-queue@0.3.0 (git+ssh://git@github.com/mllongze/bee-queue.git#8cefcb25b27c23840ca668578d3ae4bcdf4ebcd3)\r\n```\r\n\r\nAnd when I run with that, I hit the same error.  It does not resolve it for me.  I'm running Redis 3.0.3 on localhost for development.\r\n"},"comment":{"url":"https://api.github.com/repos/LewisJEllis/bee-queue/issues/comments/162964439","html_url":"https://github.com/LewisJEllis/bee-queue/issues/27#issuecomment-162964439","issue_url":"https://api.github.com/repos/LewisJEllis/bee-queue/issues/27","id":162964439,"user":{"login":"LewisJEllis","id":1445984,"avatar_url":"https://avatars.githubusercontent.com/u/1445984?v=3","gravatar_id":"","url":"https://api.github.com/users/LewisJEllis","html_url":"https://github.com/LewisJEllis","followers_url":"https://api.github.com/users/LewisJEllis/followers","following_url":"https://api.github.com/users/LewisJEllis/following{/other_user}","gists_url":"https://api.github.com/users/LewisJEllis/gists{/gist_id}","starred_url":"https://api.github.com/users/LewisJEllis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LewisJEllis/subscriptions","organizations_url":"https://api.github.com/users/LewisJEllis/orgs","repos_url":"https://api.github.com/users/LewisJEllis/repos","events_url":"https://api.github.com/users/LewisJEllis/events{/privacy}","received_events_url":"https://api.github.com/users/LewisJEllis/received_events","type":"User","site_admin":false},"created_at":"2015-12-08T18:05:31Z","updated_at":"2015-12-08T18:05:31Z","body":"Hmm, this is a bit strange. Are you waiting for the [ready](https://github.com/LewisJEllis/bee-queue#ready) queue event? It's possible to beat the caching check to the punch by not waiting for that event, but even if you're not waiting for that event, I wouldn't expect you to run into this problem if you've manually cached the scripts. There's a procedure to check if the scripts are cached on first connection, and to cache them if they're missing (and only if they're missing, so you shouldn't be running into any sort of \"tried doing something halfway through the cache repopulation\" issue). I'm a bit puzzled because the only time I've run into the NOSCRIPT error myself has been after a restart of Redis while Node is still running (as was the case in #24); I've never run into it on a clean startup of Node.\r\n\r\nThe Lua script caching being something I haven't seen other node/redis task queues utilize, of course I run into troubles with it. It seems like it would be reasonable to automatically queue commands until that ready event fires, so as to avoid some situations like this, but I'm not convinced that that would solve whatever's happening here. I'll have to do some investigation; I haven't used bee-queue on Redis 3.x yet, but hopefully that isn't the issue."}}