-
Notifications
You must be signed in to change notification settings - Fork 108
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
Error: socket hang up #594
Comments
@iraycd Can you also post some information about your environment, the driver and ArangoDB version, and what code caused this? Thanks. |
Latest docker image and latest arangojs. FROM node:lts-alpine First observed it while creating and dropping multiple databases at time. But, not I see it happening for many queries. |
request/request#2047 options.headers = options.headers || {};
options.headers["connection"] = "keep-alive"; I guess this might help. Thank you. |
That seems unlikely unless something changed in Node. Arangojs already uses keep-alive by default. I'd have to investigate this. Can you check a more recent version of Node than LTS? An unhandled rejection should cause an uncaught error in newer versions, so this would not only log the warning but actually kill the container. Sadly the stack trace doesn't really provide a lot of information. You might want to try installing this library and importing it at some point in your code: https://www.npmjs.com/package/asynctrace That might provide more detailed stacktraces that could help figuring out what's going on. |
Sorry, I am not sure how to do it JEST, I am using JEST for testing. I am using https://github.com/roboncode/orango/ to connect and disconnect. |
The text was updated successfully, but these errors were encountered: