Closed danbryan closed 1 year ago
This is happening because our function to get TXs at that block height isn't finding anything... not sure why that is yet, but we are not returning the data from the query b/c we don't have it. I was wrong
This looks like it might be a lens bug...
I am still unable to repro this. Every time I test this locally it works. @KyleMoser would you mind testing this on your machine? Otherwise, @danbryan let's hop on a screenshare again and see if we can make more headway troubleshooting this. We can do what we did yesterday where I commit logging changes and you run on your end and we can try to figure out where things diverge.
Finally able to repro this! It looks like it has to do with the config used when querying the chain. If you use the cosmos hub config you get the issue, if you use the osmosis one it works. Still need to figure out why, but we now have something to go on.
[log]
level = "info"
pretty = true
[base]
addressRegex = "cosmos(valoper)?1[a-z0-9]{38}"
addressPrefix = "cosmos"
# startblock = 8900000
startblock = 9596578
endblock = 13349069
throttling = 0.0005
rpcworkers = 8
blockTimer = 1000
waitForChain = false
waitForChainDelay = 5
indexingEnabled = true
exitWhenCaughtUp = false
osmosisRewardsOnly = false
[lens]
rpc = "http://35.223.140.66:26657"
key = "default"
accountPrefix = "cosmos"
keyringBackend = "test"
chainID = "cosmoshub-4"
chainName = "cosmoshub"
[database]
host = "10.245.0.3"
port = "5432"
database = "tax"
user = "taxuser"
password = "8qrxxc2cdduu4csqze83a"
logLevel = "warn"
If you look at the mint scanTX
Transaction: https://www.mintscan.io/cosmos/txs/9958FD46539C74ABACA09C5A095BDBA6EBAD2A4CDFF5EF1542A6117411217E69
Someone paid, 0.000750ATOM to send 5.000000ATOM
However, the CSV report, ONLY shows the fee. Not the 5 ATOM being sent.
Address: cosmos1dm68mx9jcsyqkyzp3up7gmnu3ku84v8gf6v75u
events.csv
user/pass: https://defiant-corp.slack.com/archives/C047V094DGA/p1671481968917959
command: