-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
Error: Callback was already called. #10
Comments
My coworker just submitted a pull request for this issue: |
@mpalmerlee Thanks for the heads up! The patch of #11 is merged and released |
Yeah, it looks good with version 0.0.6 thanks! Might want to add some tests against memcached with an async call, that's what exposed this issue. |
@mpalmerlee I think a test should be added in Jackpot against this to prevent double function calls. |
We just started seeing this error in our development servers related to using the node-memcached package. since it specifies jackpot version >= 0.0.2 with the recent 0.0.5 release we started seeing this error.
at EventEmitter.memcached.delegateCallback (...node_modules/memcached/lib/memcached.js:622:12)
at EventEmitter.rawDataReceived (...node_modules/memcached/lib/memcached.js:681:22)
at EventEmitter.BufferBuffer (...node_modules/memcached/lib/memcached.js:613:12)
at Socket.bowlofcurry (...node_modules/memcached/lib/utils.js:108:15)
We can shrink wrap our way out of this issue, but wanted to let you know.
thanks,
-Matt
The text was updated successfully, but these errors were encountered: