srknzl

this same thing causes a test fail if console.log is stubbed and `console.log.restore()` is called later on. To fix this I assigned spy to a variable then use restore() on...

Might be possible, but It is much harder to modify a symbol key.

@yuce this is fixed but the issue still happens unreleased branches. maybe it is a good idea to keep the issue until every maintenance release is released

Another similar one: ``` 1) CPSessionManagerTest CPProxySessionManager acquireSession: should create new session for existing invalid session: Uncaught TypeError: Cannot read property 'invokeOnRandomTarget' of undefined at CPSessionManager.requestHeartbeat (src\proxy\cpsubsystem\CPSessionManager.ts:40:17) at heartbeatTask (src\proxy\cpsubsystem\CPSessionManager.ts:40:17)...

We need to backport this to all other branches as well

@marinrusu1997 If you can reproduce, can you run again and send the logs when the TRACE logging is on? ```js const client = await Client.newHazelcastClient({ clusterName: '@FIXME YOUR CLUSTER NAME',...

Opened a fix PR https://github.com/hazelcast/hazelcast-nodejs-client/pull/1377 Probably, the leak happens in the older versions of the client as well. We need to confirm. For example, the problematic code causing the bug...

@marinrusu1997 The memory leak is fixed. Thanks for reporting this. We appreciate it.

Hi I did not get a compilation error with this code: ```ts import {Client} from "hazelcast-client"; async function main() { const client = await Client.newHazelcastClient(); const aMap = await client.getMap("a");...

You may get away from the error for now by setting `skipLibCheck` to `true` as mentioned in https://github.com/hazelcast/hazelcast-nodejs-client/issues/1286#issuecomment-1121586700