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

network.js failed to reroute command to the next peer: Cannot read property 'responseHandlers' of undefined #12

Closed
pmiklos opened this issue Feb 5, 2017 · 1 comment

Comments

@pmiklos
Copy link
Contributor

pmiklos commented Feb 5, 2017

My headless-byteball wallet died with the error below (on Jan 31). The byteballcore version was 0.1.35

/home/pi/headless-byteball/node_modules/byteballcore/network.js:171
				ws.assocPendingRequests[tag].responseHandlers.forEach(function(rh){
				                            ^

TypeError: Cannot read property 'responseHandlers' of undefined
    at /home/pi/headless-byteball/node_modules/byteballcore/network.js:171:33
    at /home/pi/headless-byteball/node_modules/byteballcore/network.js:251:11
    at tryFindNextPeer (/home/pi/headless-byteball/node_modules/byteballcore/network.js:266:3)
    at findNextPeer (/home/pi/headless-byteball/node_modules/byteballcore/network.js:249:2)
    at EventEmitter.<anonymous> (/home/pi/headless-byteball/node_modules/byteballcore/network.js:255:4)
    at EventEmitter.g (events.js:291:16)
    at emitOne (events.js:101:20)
    at EventEmitter.emit (events.js:188:7)
    at /home/pi/headless-byteball/node_modules/byteballcore/network.js:577:13
    at /home/pi/headless-byteball/node_modules/byteballcore/network.js:203:3
@tonyofbyteball
Copy link
Member

fixed by bac1431

tonyofbyteball pushed a commit that referenced this issue Aug 19, 2019
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

2 participants