-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
TypeError: Cannot read property 'length' of undefined #118
Comments
I can provide the output of the getblockbynumber for 171620 & 171621 if needed. Please let me know. Thanks. |
Just found this in my explorer output as I run the npm start before attempting the update - { Error: No information available about transaction |
It will oddly enough let me manually add blocks to the block explorer using the api, but wont pick them up on its own after block 171620. Anyone have even the slightest clue? |
try to reindex your daemon and run index reindex or index check |
I've tried deleting & redownloading the block chain for the daemon, then running index reindex & it still gives me /explorer/lib/explorer.js:344 index check also gives me this error ^^^ I havent tried starting the daemon with the -reindex flag, then running index reindex, so I'll try that, wouldnt hurt at this point lol |
Well, I've tried everything above with no luck. Not sure what else to do... Interesting to note that if I search blocks with the api, they'll get added to the database & will display in the block explorer, but it wont pick up the blocks on it own with index update, reindex and check. |
try in file explorer.js in function change value 100 to 30 (or other smaller) |
Thanks for the suggestion, I tried updating with no luck but I'm reindexing with the changes now & my fingers crossed! I'll report back with what I find. |
I tried to update first then reindex with the same result /: |
Looks like block 171621, the one it wont sync past, has a non-standard transaction, but this commit looks like it should've taken care of this issue? |
did anyone figure out what the issue is ? is there any fix ? |
TypeError: Cannot read property 'length' of undefined |
|
@blakey12345 where do i have to implement your code in order to be able to execute the index command correctly? Edit: figured it out. Thanks anyways :) |
Where does this go? Is there an official pull request? |
blakey's snippet references |
I revised /lib/explorer.js Line 341 with above code, but still get length error. |
As do i @leegod |
I used the code provided by blakey, but still getting the same issue also (Cannot read property 'length' of undefined) |
Duplicate of #56 |
Hello All! Thank you for the great work & support! Wondering if anyone has ran into this issue before -
/explorer/lib/explorer.js:344
module.exports.syncLoop(tx.vout.length, function (loop) {
^
TypeError: Cannot read property 'length' of undefined
at /root/explorer/lib/explorer.js:344:42
at Request._callback (/root/explorer/lib/explorer.js:114:14)
at Request.self.callback (/root/explorer/node_modules/request/request.js:187:22)
at emitTwo (events.js:125:13)
at Request.emit (events.js:213:7)
at Request. (/root/explorer/node_modules/request/request.js:1044:10)
at emitOne (events.js:115:13)
at Request.emit (events.js:210:7)
at IncomingMessage. (/root/explorer/node_modules/request/request.js:965:12)
at emitNone (events.js:110:20)
at IncomingMessage.emit (events.js:207:7)
at endReadableNT (_stream_readable.js:1059:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
Whatever I try, I cant get it to sync past a block 171620. Neither index update, index reindex & index check will get past that block 171620. If anyone can point me in the right direction I'd appreciate it.
Thank you!
The text was updated successfully, but these errors were encountered: