Ștefan Rusu

Hi. Sorry for replying so late. I was away from keyboard (in a place with poor to no Internet access). I'm going to merge this, but the "next" branch is...

Hello, I'll "merge" this into the [next](https://github.com/SaltwaterC/aws2js/tree/next) brach where the development is happening. I'm dropping all the legacy code in favour of a clean start. I'm pretty close to a...

Hi Stefan, I've to admit that I haven't checked the persistent connection behaviour as I wrote this library for a service that uses lots of different URLs (a file mirroring...

An code example proving the issue is always welcome.

Thank you for your patch. I applied it to the future branch and rebuilt the documentation. This PR will be closed automatically as soon as I push a new release...

Yep. Non-native speaker is non-native. Merged your changes into the future branch and pushed the actual changes to gh-pages. It will appear as merged, per GitHub, once the master branch...

Hi. There's nothing I can do as this is related to libxmljs/libxmljs#546. There's a fork that works on node 12, but that's outside of the scope.

Ran into this pain about a week ago when ChefDK 0.17.17 was released. The issue is due to [this commit](https://github.com/test-kitchen/test-kitchen/commit/12e4dadcd561e57d7ac8c1824740992c8e1a9d48) in SSH transport. I've monkey-patched the connection_options method (essentially rolling...

Here's a gist to reproduce the issue: https://gist.github.com/SaltwaterC/85711798d0de908d905a8ca23392be75 Setup: ChefDK 0.17.17 (recommended, TK 1.11+ necessary) + kitchen-docker 2.5.0 + working Docker setup. Bear in mind to use `rake converge` instead...

Hey. Thanks for getting back to me. I think anything would work. I believe this should be an error, but I can live with a warning. At least that would...