Open dplewis opened 3 weeks ago
So initialized
is the state after calling the ParseServer
constructor. As soon as you call start()
on the instance, the state changes to starting
. From what you describe it looks like start()
has not been called at all, because starting
is set synchronously after calling start()
. So it may be related to the reconfigureServer
logic; that promise may return early, rather than the server init itself. Which would be good, because that means it's only a testing issue, not a server issue.
Re-opened, I think we first need to upgrade the Parse JS SDK in Parse Server to see whether the Parse Server CI shows less flakiness.
I agree, I still don’t know why this is happening. I would like to think I solved it on the JS SDK
Issue still occurs in recent PRs; I have never seen this before; is this a recently introduced issue?
New Issue Checklist
Issue Description
The test suite in this repo and in the JS SDK both have flaky tests. I believe this is due to the asyncronous nature of starting the server instance.
I think the issue is after the promise resolves the server is still initializing. https://github.com/parse-community/parse-server/pull/8232
Steps to reproduce
I can't reproduce this locally
Actual Outcome
Tests fail
Expected Outcome
Test Pass