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
Issue:
ctrl-c kills the parse-server, but not the live-query server.
This issue arises when:
I am doing local cloud code development on my laptop.
I am running the live-query server in the same process as the parse server. Starting server with npm start
When I try to cycle the parse-server using ctrl-c (SIGINT) or kill pid (SIGKILL) the process for the livequery server doesn't die. Attempts to restart the server with npm start will fail with a port in use message (Unable to listen on port 8082. The port is already in use.).
Server
parse-server version (Be specific! Don't say 'latest'.): true on 2.7 and master
Operating System: osx 10.13.4
Hardware: mbp (late 2016)
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): localhost
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Issue:
ctrl-c kills the parse-server, but not the live-query server.
This issue arises when:
npm start
kill pid
(SIGKILL) the process for the livequery server doesn't die. Attempts to restart the server withnpm start
will fail with a port in use message (Unable to listen on port 8082. The port is already in use.
).The text was updated successfully, but these errors were encountered: