From 08084bff7f2b8f0a9b9a852acbf81be9e8587d7e Mon Sep 17 00:00:00 2001
From: bluesbrothers2k <j.meister@bossmail.de>
Date: Tue, 9 Jan 2018 15:46:22 +0100
Subject: [PATCH] Fix longRunner error in local_comms.js

This fix solves the longRunner throwing errors after updating to NVM 8.9.3. Should solve problems described in #217 and #230.
---
 lib/local_comms.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/local_comms.js b/lib/local_comms.js
index 17c9975..0e8335e 100644
--- a/lib/local_comms.js
+++ b/lib/local_comms.js
@@ -635,7 +635,7 @@ function Database(){
                     debug("Scanning block: " + blockID);
                     let txn = global.database.env.beginTxn({readOnly: true});
                     let cursor = new global.database.lmdb.Cursor(txn, global.database.shareDB);
-                    for (let found = (cursor.goToRange(blockID) === blockID); found; found = cursor.goToNextDup()) {
+                    for (let found = (cursor.goToRange(parseInt(blockID)) === blockID); found; found = cursor.goToNextDup()) {
                         if (pplnsFound){
                             cursor.getCurrentBinary(function(key, data) {  // jshint ignore:line
                                 if (blockList.indexOf(key) === -1){