This repository was archived by the owner on Dec 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 50
how to shutdown server #38
Comments
Ideally we'd have a function we could invoke that would terminate the spawned process. But in the meantime, I hope this unblocks folks:
Don't forget to pass in your port if it's not the default. There's probably some slicker mongo-fu out there. Answer provided without warranty, etc. etc. References: |
this is great, thank you, I will add a helper function. |
Any updates? @winfinit should be easy to provide a function to exit the child process. Do you accept PR? |
Hello Dusting,
PRs are always welcome! I’ve meant to fix this one for a while now, but just didn’t get around it yet.
… On Aug 10, 2017, at 9:58 AM, Dustin Deus ***@***.***> wrote:
Any updates? @winfinit <https://github.com/winfinit> should be easy to provide a function to exit the child process. Do you accept PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIeWZnYu5LPCB5KuEpRqkd6ZG9TwFIeks5sWwxwgaJpZM4NMP9Z>.
|
deployable
added a commit
to deployable/mongodb-prebuilt
that referenced
this issue
Feb 1, 2018
Mocha 4+ changed behaviour to "no longer force the process to exit once all tests complete" so async tasks will keep the test run from completing, the prebuilt-mongod daemon is such a task This adds helper functions to allow a test to finish `stop()` will send a `SIGINT` to cleanly shutdown `kill()` will send a `SIGTERM` Fixes mongodb-js#38
LoneRifle
pushed a commit
that referenced
this issue
Nov 26, 2018
Mocha 4+ changed behaviour to "no longer force the process to exit once all tests complete" so async tasks will keep the test run from completing, the prebuilt-mongod daemon is such a task This adds helper functions to allow a test to finish `stop()` will send a `SIGINT` to cleanly shutdown `kill()` will send a `SIGTERM` Fixes #38
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the documentation you mention that via the mongodb helper the server can be started.
Is there any way to shutdown that server instance programatically?
The text was updated successfully, but these errors were encountered: