Open evtimmy opened 1 week ago
I did debug the initialization of the server and saw that ParseLiveQueryServer creates its own cacheController instance:
but that instance connect() is never called. The regular ParseServer does call connect() on its own instance of the cache when initializing the startup promises.
This used to work in earlier versions of parse-server, before we switched to redis 4 client as redis 4 requires the async connect() to be explicitly called before using the client, whereas redis 3 automatically called connect() if the client was not connected.
One simple fix would be to add initialization await this.cacheController.connect()
here:
I'm just not clear on why we check this.subscriber.isOpen and if this connect() may be called multiple times, or only on startup?
Issue Description
Running ParseLiveQueryServer where a RedisCacheAdapter is also configured causes crash when ParseLiveQueryServer tries to use the cache adapter.
Steps to reproduce
Actual Outcome
Expected Outcome
LiveQueryServer post update to client
Environment
Server
7.4.0-alpha.5
Azure
Client
iOS/Android
Workaround:
disable the redis cache adapter.