You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that bitcoind's getrawtransaction sometimes returns an empty/blank transaction for some people, which causes the following error:
Traceback (most recent call last):
File "/home/local/counterpartyd_build/dist/counterpartyd/counterpartyd.py", line 504, in <module>
blocks.follow()
File "/home/local/counterpartyd_build/dist/counterpartyd/lib/blocks.py", line 402, in follow
source, destination, btc_amount, fee, data = get_tx_info(tx)
File "/home/local/counterpartyd_build/dist/counterpartyd/lib/blocks.py", line 307, in get_tx_info
for vout in tx['vout']:
TypeError: 'NoneType' object is not subscriptable
In my case, I tried rerunning bitcoind with --txindex=1 --reindex=1 to no avail. Same issue (although I'm not ruling out user error on my end :).
This happens due to bitcoind's JSON RPC getrawtransaction returning:
{'result': None, 'id': 0, 'error': {'message': 'No information available about transaction', 'code': -5}}
Two recommended things:
Do better error checking from bitcoind api responses (especially where there is an 'error' attribute or "'result': None" in the data output)
Figure out why bitcoind is returning this in some cases, and address
The text was updated successfully, but these errors were encountered:
Nevermind, I had counterpartyd accessing a different bitcoind instance on my machine that was not using txindex=1 ...modified it to use one that did.
Enhancing counterpartyd to provide this feedback (e.g. "do you have txindex=1 in your bitcoind.conf file??") on reception of this error would be helpful I think.
Nevermind, I had counterpartyd accessing a different bitcoind instance on
my machine that was not using txindex=1 ...modified it to use one that
did.
Enhancing counterpartyd to provide this feedback (e.g. "do you have
txindex=1 in your bitcoind.conf file??") on reception of this error would
be helpful I think.
Reply to this email directly or view it on GitHub: #4 (comment)
It seems that bitcoind's getrawtransaction sometimes returns an empty/blank transaction for some people, which causes the following error:
In my case, I tried rerunning bitcoind with --txindex=1 --reindex=1 to no avail. Same issue (although I'm not ruling out user error on my end :).
This happens due to bitcoind's JSON RPC getrawtransaction returning:
Two recommended things:
The text was updated successfully, but these errors were encountered: