You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2021. It is now read-only.
While improving the tests in #169 (comment) occasionally the serve process on port 8000 is not terminated, causing subsequent tests to fail, or trying to start the server locally.
The server has been observed to not terminate specifically when using then --no-docker flag, although this is not 100% reproducible. Without the --no-docker flag we weren't able to reproduce this behaviour yet.
Worth noting: in #169 we bumped the usage of latest TechDocs common package, and use the default docker image provided by it
While improving the tests in #169 (comment) occasionally the
serveprocess on port 8000 is not terminated, causing subsequent tests to fail, or trying to start the server locally.The server has been observed to not terminate specifically when using then
--no-dockerflag, although this is not 100% reproducible. Without the--no-dockerflag we weren't able to reproduce this behaviour yet.Worth noting: in #169 we bumped the usage of latest TechDocs common package, and use the default docker image provided by it
This is a follow-up from
Possibly related:
Expected Behavior
npx @techdocs/cli serve --no-dockerornpx @techdocs/cli serve:mkdocs--no-dockerSIGTERMCurrent Behavior
techdocs-cli serve --no-dockerortechdocs-cli serve:mkdocs--no-dockerSIGTERMYour Environment