-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
QueryStream broken in Node 4 and 6 (2.1) #847
Labels
Comments
wubzz
changed the title
QueryStream broken in Node 4 and 6
QueryStream broken in Node 4 and 6 (2.1)
Feb 15, 2018
Hmm. |
@dmcghan and @anthony-tuininga have a fix:
When the world (i.e. the Windows people in the team) wake up and we can get Windows binaries built, we'll push a v2.1.1. After Spring holiday is over and everyone is back at work, we'll have a postmortem to work out how this got missed! |
I've released 2.1.1. Give it a whirl! |
It works! :) 🎉 |
@elhigu yay! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your Node.js version? Is it 64-bit or 32-bit? Run
version.js
from64-bit v4.8.7 & v6.13.0
What is your node-oracledb version?
Latest
What error(s) you are seeing?
After this commit our CI tests over at knex started breaking with the above error message. After some digging I realized that
.destroy
was added toReadableStream
in node 8+, which means the current version of the lib does not work for Node < 8.The README states
The text was updated successfully, but these errors were encountered: