get_consensus_at doesn't work in version 0.0.7 becaus

I added from config import log which solves the <code

Here is the output of the two commands now: <div class="snippet-clipboard-content

get_consensus_at broken: no logger in utils.py about stacks.js HOT 3 CLOSED

larrysalibra commented on August 26, 2024

get_consensus_at broken: no logger in utils.py

from stacks.js.

Comments (3)

larrysalibra commented on August 26, 2024

I added from config import log which solves the NameError but now getting other strange errors:

root@blockchainid:~# blockstore-cli get_consensus_at 385159
[DEBUG] [utils:40] (14105) ERROR in pretty print: expected string or buffer
null
root@blockchainid:~# nano +876 /usr/local/lib/python2.7/dist-packages/blockstore_client/utils.py
root@blockchainid:~# blockstore-cli get_consensus_at 385100
[DEBUG] [utils:40] (14111) ERROR in pretty print: No JSON object could be decoded
"f"
root@blockchainid:~# blockstore-cli get_consensus_at 385000
1
root@blockchainid:~# blockstore-cli get_consensus_at 384000
0
root@blockchainid:~#

from stacks.js.

larrysalibra commented on August 26, 2024

get_nameops_at also seems affected by this (or something similar)

root@blockchainid:~# blockstore-cli get_nameops_at 385000
[DEBUG] [utils:40] (14166) ERROR in pretty print: expected string or buffer
[]
root@blockchainid:~#

from stacks.js.

muneeb-ali commented on August 26, 2024

Here is the output of the two commands now:

(blockstore-client)muneeb@amsterdam:bin$ ./blockstore-cli get_consensus_at 384000
{
    "result": "00bc6f1800ea01674bcad0fdad8a1839"
}

and

(blockstore-client)muneeb@amsterdam:bin$ ./blockstore-cli get_nameops_at 385000
{}

As, @jcnelson mentioned that we're going to take another pass over the JSON RPC interface. And will be improving return formats etc of individual RPC calls.

from stacks.js.

Recommend Projects