From 5be08b71f49fbe1f7fb3899737d0fbaa9e6b0f86 Mon Sep 17 00:00:00 2001
From: Jose-Luis Landabaso <landabaso@gmail.com>
Date: Fri, 4 Nov 2022 19:46:31 +0100
Subject: [PATCH] Do not log errors after closing the connection.

I decided to push changes to this fork of electrum-client since it is actually being used in production.

On rare occasions the client logs errors after close().
This is because pingTimer timeout sometimes is not cleared.
It looks like after closing, server_ping may be in a state where it doesn't throw and doesn't resolve either.
---
 index.js | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/index.js b/index.js
index 5037dd5..1d2dcf3 100644
--- a/index.js
+++ b/index.js
@@ -61,7 +61,9 @@ class ElectrumClient extends Client {
     this.timeout = setTimeout(() => {
       if (this.timeLastCall !== 0 && new Date().getTime() > this.timeLastCall + 5000) {
         const pingTimer = setTimeout(() => {
-          this.onError(new Error('keepalive ping timeout'));
+          if (this.timeout != null) {
+            this.onError(new Error('keepalive ping timeout'));
+          }
         }, 9000);
         this.server_ping().catch((reason) => {
           console.log('keepalive ping failed because of', reason);
@@ -75,6 +77,7 @@ class ElectrumClient extends Client {
     super.close();
     if (this.timeout != null) {
       clearTimeout(this.timeout);
+      this.timeout = null;
     }
     this.reconnect = this.reconnect = this.onClose = this.keepAlive = () => {}; // dirty hack to make it stop reconnecting
   }