-
Notifications
You must be signed in to change notification settings - Fork 108
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
Warning: a promise was created in a handler at lib/pool.js:248:14 but was not returned from it. #285
Comments
Fixed in 2.3.22 |
nopnop
added a commit
to nopnop/rethinkdbdash
that referenced
this issue
Sep 14, 2016
Bluebird default behavior is to warn on un-returned promise. This PR fix many of those in cursor.js
@neumino Your fix didn't fix it fully. |
@neumino Just bumping this up again. Need to re-open this issue. |
Can you send a PR? |
thejsj
added a commit
to thejsj/rethinkdbdash
that referenced
this issue
Dec 17, 2016
* 'master' of github.com:neumino/rethinkdbdash: (304 commits) Fix leaked variable from test Bump to 2.3.27 Fix neumino#313 Bump to 2.3.26 fix: return null where new Promises are created but not returned Fix leak in tests Fix leak in tests Bump to 2.3.25 Make identification errors operational such that they can be properly caught - Fix neumino#295 Bump to 2.3.24 Close the stream if an error is emitted since we can't recover frm it Remove the use of Buffer with new for node 7 - Fix neumino#304 Wrap sending the proof in a try/catch in case the connection is closed - Fix neumino#296 Bump to 2.3.23 Prevent bluebird warning - Fix neumino#287 Bump to 2.3.22 Prevent bluebird warning - Fix neumino#285 function r: remove unused parameter `options` readme: minor typo fix Bump to 2.3.21 ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using
thinky#2.3.6
and that pulled downrethinkdbdash#2.3.21
. I only ran into this when I started to use thepingInterval
option.Here's the full error:
To fix it, I put in return statements at the line specified above, and also on line: 321. Not sure that is the correct fix though, so I haven't created a PR.
The text was updated successfully, but these errors were encountered: