Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blocks.map is not a function #666

Open
SoapyFresh opened this issue Mar 28, 2021 · 4 comments
Open

blocks.map is not a function #666

SoapyFresh opened this issue Mar 28, 2021 · 4 comments

Comments

@SoapyFresh
Copy link

Using latest node version 12.21.0
The pool is finding blocks, but gets this error after receiving enough confirmations.

TypeError: blocks.map is not a function
at /home/pool/newpool/pool/lib/blockUnlocker.js:120:31
at nextTask (/home/pool/newpool/pool/node_modules/async/dist/async.js:4576:27)
at next (/home/pool/newpool/pool/node_modules/async/dist/async.js:4584:13)
at /home/pool/newpool/pool/node_modules/async/dist/async.js:321:20
at /home/pool/newpool/pool/lib/blockUnlocker.js:113:5
at /home/pool/newpool/pool/node_modules/async/dist/async.js:2420:29
at wrapper (/home/pool/newpool/pool/node_modules/async/dist/async.js:268:20)
at iteratorCallback (/home/pool/newpool/pool/node_modules/async/dist/async.js:493:17)
at /home/pool/newpool/pool/node_modules/async/dist/async.js:321:20
at /home/pool/newpool/pool/node_modules/async/dist/async.js:2417:17
at /home/pool/newpool/pool/lib/blockUnlocker.js:104:6
at /home/pool/newpool/pool/lib/apiInterfaces.js:66:3
at IncomingMessage. (/home/pool/newpool/pool/lib/apiInterfaces.js:41:5)
at IncomingMessage.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1241:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)

@element0355
Copy link

Also having the same issue. Did you find a fix?

@SoapyFresh
Copy link
Author

Also having the same issue. Did you find a fix?

No I have not!

@element0355
Copy link

element0355 commented Apr 13, 2021

I found a temporary solution. In v2.0 config.json I set the unlocker enable to false. I then had a copy of v1.3.5. I installed that in a separate folder. I then copied config.json and /lib/blockUnlocker.js from v2.0 to v1.3.5 folder. Set the unlocker enable true and then ran node init.js -module=unlocker in v1.3.5, and ran the pool as normal in v2.0 folder. It seems to being working, it is unlocking the blocks and updating pending payments for my miners.

@StarlightJS
Copy link
Contributor

The solution that really worked for me is to change the package async in package.json to 1.5.2.

Happy mining everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants