-
Notifications
You must be signed in to change notification settings - Fork 629
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
Keep alive issue #43
Comments
I believe this was resolved in 59e1fca - can you confirm? |
I was running into the same issue for geocoding calls and can confirm that the problem is resolved on the current master branch. However, the latest npm package 0.2.1 is not up to date with master. Will you be pushing out an updated package? |
i can confirm that the latest npm version still has the bug.
|
If been using the directions and the geocoding calls to the Maps API and both of them seem to have an issue. after firing a request and handling the response node doesn't exit the script due to the keep alive's in the response. isn't there a way to manipulate the request in a way, that the connection is not kept alive, or a call to actively close the connection (process.exit is not an option)
The text was updated successfully, but these errors were encountered: