Nikolay Karadzhov
Nikolay Karadzhov
Hi @Eomm, if you are still up to it, we can resurrect this PR and finish it
I guess thats fine. Thanks for the contribution!
@Eomm sorry, i clicked "merge" without looking. This is supposed to be merged agains `master`, not `v5`. Could you reopen against master?
@JulienZD thanks for flagging this out. Im not sure if we can easily fix this, but I will investigate
Hi all, really sorry about this! We are working to resolve this. Its complicated and will most likely result in a breaking change.
Hi everyone, thanks to @PavelPashov, we now have a mitigation for this issue. It reduces time/memory for compilation around x4 on my machine. We have put that fix in [the...
Closing this as the issue seems to be fixed in version 5
@edrose I dont see the issue here. Even though `this.#connect().catch(() => {}))` swallows the error, #connect will still emit an `error` event, which will in turn trigger `#onSocketError`, continuing in...
@edrose AFAIK the only thing that controls when the library will choose to stop retrying is the reconnectStrategy, which is controlled by the user. So, you have to return `false`...
@edrose what do you think?