Skip to content

Conversation

@brianc
Copy link
Owner

@brianc brianc commented Jan 28, 2020

This is the exact same as #2081 except it targets master, so this closes #2081 since this is not a backwards incompatible change: the old behavior was simply to put your pool into an unusable or unknown state and eventually perhaps crash your app sometime in the future when you go to use the broken client later which is...never what you want.

johanneswuerbach and others added 5 commits January 28, 2020 09:19
If a client is not queryable, the pool should prevent requeuing instead
of strictly enforcing errors to be propagated back to it.
Some weird behavior changed w/ async iteration in node 13.7...I'm not sure if this was an unintentional break or not but it definitely diverges in behavior from node 12 and earlier versions in node 13...so for now going to run tests on 13.6 to unblock the tests from running while I track this down.
Co-Authored-By: Charmander <~@charmander.me>
@brianc brianc merged commit 727f1a0 into master Jan 28, 2020
@brianc brianc deleted the bmc/fix-pool-return-error branch January 28, 2020 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants