fix: flow control in message-io.js

[chdh]

Fix for #877

@arthurschreiber could you have a look at this? In Tedious 2.7.0 you changed the data flow architecture to a stream of streams. The inner stream must also be paused.

[arthurschreiber]

Thank you @chdh for preparing this, and sorry for having broken this with the 2.7.0 release. Do you have a suggestion how we could add a test to ensure we don't regress on this again on the future?

[arthurschreiber]

@chdh FYI, I tweaked the implementation a tiny bit.

[arthurschreiber]

🎉 This PR is included in version 6.0.1 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[chdh]

@Arthur Thanks for your fix. This is the better solution. And thanks for merging and releasing so quickly.

[chdh]

Do you have a suggestion how we could add a test to ensure we don't regress on this again on the future?

We could do the same thing as in my test program (published with #877): Start a very large query, pause it and see if the memory increases signiffically. But that would be a relatively unstable and unreliable method.