-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Uncaught Exception: TypeError: Cannot destructure property 'resolve' of '__classPrivateFieldGet(...).shift(...)' as it is undefined #2626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Probably a duplicate of #2417 |
hey @leibale, it looks like we just hit into this problem recently:
We are already on the latest version of redis |
Same here, node-redis 4.7.0, node 18.14.0. But in our case we have a client-facing gRPC service, that when a stream is initiated we perform a pSubscribe for that stream call. If the gRPC client<->server socket crashes for whatever reason (like a proto serialization error), and we don't call I'm thinking it might have something to do with garbage collection, since the redis connection and client object live inside the gRPC call initiator / scope. When node kills the gRPC client the redis object goes with it, without us having a chance to call unsubscribe or disconnect.
|
Hi, same here, even with #2653. For us it happens after failovers when we use CLIENT KILL to force clients to reconnect to the new master.
|
Uh oh!
There was an error while loading. Please reload this page.
Description
Hello 👋🏻
Starting to add some resillency to our codebase and I was testing what would happen when the max clients have been reached.
I have ran
config set maxclients 1
in my Redis server and started the project to see how this would be handled.This fails with the following:
Node.js Version
18.17.1
Redis Server Version
7.2.1
Node Redis Version
4.6.10
Platform
MacOS (Docker redis-stack)
Logs
The text was updated successfully, but these errors were encountered: