Closed neilstevenson closed 1 year ago
Internal Jira issue: API-1906
Will close this one because this is a known issue and tracked at https://github.com/hazelcast/hazelcast-nodejs-client/issues/982. We want to add UnknownProxy type that we will return when we encounter with a proxy that is not supported in the Node.js client.
Describe the bug This is thrown
Expected behavior No exception
Screenshots N/a
Environment (please complete the following information):
Exact Node.js client version that you use (e.g.
4.1.0
):5.2.0
Exact Hazelcast version that you use (e.g.
4.0.1
, also whether it is a minor release, or the latest snapshot):Hazelcast Platform 5.3.0-SNAPSHOT (20230227 - fb61178)
Cluster size, i.e. the number of Hazelcast cluster members. 3
Number of clients: 1
Java version. It is also helpful to mention the JVM parameters: Java 17
Node.js version. It is also useful to mention
node
command line arguments if there are any: node:18.14, npm@9.5.0Operating system. If it is Linux, kernel version is helpful:
library/node:18.14
Docker imageLogs and stack traces, if available: As above
To Reproduce Using
Additional context This does not occur testing on localhost against a 1 or 2 node cluster, but does on Kubernetes