Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix ECONNRESET in Mocha suite #56

Closed
jacoscaz opened this issue Oct 9, 2017 · 1 comment
Closed

Fix ECONNRESET in Mocha suite #56

jacoscaz opened this issue Oct 9, 2017 · 1 comment
Assignees
@jacoscaz
Labels
bug

Comments

@jacoscaz
Copy link
Owner

jacoscaz commented Oct 9, 2017

It seems like there's no way to force the ldf-client instance to close its connection to the server before the latter calls socket.destroy(). This triggers a ECONNRESET error - currently unhandled - that breaks the mocha suite.

Related issue on ldf-client's repo: LinkedDataFragments/Client.js#39
@jacoscaz jacoscaz added the bug label Oct 9, 2017
@jacoscaz jacoscaz self-assigned this Oct 9, 2017
@jacoscaz jacoscaz added this to the v3.0 - SPARQL milestone Oct 9, 2017
@jacoscaz
Copy link
Owner Author

jacoscaz commented Oct 12, 2017 •
edited
Loading

Used https://github.com/hunterloftis/stoppable as a workaround. It augments native http.Server instances with a .stop() method that closes all connections, keep-alive ones included, but waits until each becomes idle (no in-flight requests) before doing so. Also see nodejs/node#2642.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jacoscaz jacoscaz

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacoscaz