Open itsciccio opened 4 months ago
@itsciccio
This could be 1 of 2 possible issues:
I will test this out myself to see if its possible to query it from probe.
Thanks for the reply @pharr117. Let me know of any updates on the matter. I probably think its a node issue due to a deprecating change.
However, I also noticed that I was unable to fetch a few Osmosis blocks, for example 551165
, as probe was unable to retrieve the block results for the block.
Got status, some data follows:
Node moniker: Simply Staking: Archive Node NL
Got block, some data follows:
Height: 551165
Error getting block results
error in json rpc client, with http response metadata: (Status: 200 OK, Protocol HTTP/1.1). Failed to read response body: unexpected EOF
Highly unlikely it is probe-related, as it is probably once again due to node versioning problems. However if you do get the chance to try querying it, would be appreciated also.
@itsciccio A few things to note on Probe that I feel may block you later on down the road:
Defiant's Osmosis-specific solution to this was to:
This gets around Codec issues, but is Osmosis-specific in that:
Both methods are pretty brittle and hard to maintain, but we found success in both.
tl;dr
What you may be looking for is the Defiant Lens fork branch v0.0.19-dl
Using
main.go
, I am trying to query block3513
from an Osmosis Archive Node. Although I am able to retrieve the block, I am unable to retrieve the transactions with the following error message:I have also attempted to add the following lines to the
MakeCodec
function, with the hopes of the system being able to recognize theMsgCreatePool
transaction, however had no luck:Is there something I am doing incorrectly, or is this a bug?
NB: Querying other blocks not containing this transaction type works as intended.
TIA