Closed
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
There is a flaky test on the JS SDK and I believe it is caused by the liveQueryServer not shutting down when the server shuts down. The server is shutdown but there are still connections to the liveQueryServer. This may have unwanted effects. Also there are flaky tests on the server that could be addressed
https://github.com/parse-community/Parse-SDK-JS/actions/runs/4011772368/jobs/6889651856
Steps to reproduce
- Start server with
startLiveQueryServer: trueconfiguration - Call
server.handleShutdown() - Call
server.close() - Check if live query server is still running
Actual Outcome
LiveQueryServer is still opened
Expected Outcome
LiveQueryServer is closed
Alternatives / Workarounds
In production I use a dedicated live query server instead of the internal configuration which is recommended so I never see this issue.
Environment
Server
- Parse Server version:
6.0.0 - Operating system:
Mac - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
local
Database
- System (MongoDB or Postgres):
Mongo - Database version:
4.4 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
local
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc):
Javascript - SDK version:
4.0.0