cannot query with height in the future

[flcoder]

Ethers Version

5.6.9

Search Terms

cannot query with height in the future

Describe the Problem

"rpc error: code = Unknown desc = cannot query with height in the future; please provide a valid height: invalid height"

I am developing for Cronos and I constantly get this error at random, I might get it 200 times before finally it doesn't throw. I have to loop and catch the exception, ignore it and try again. Eventually it doesn't throw that error, but it's really annoying and there's nothing on the internet to give even a slight hint about what's causing this error.

I'm actually not sure this has anything to do with Ethers.js, but I'm not sure what software I need to look into to figure out why this happens.

If I google this error, I only get 4 links which have no information. TIA if anyone can clue me in.

Code Snippet

No response

Contract ABI

No response

Errors

Object
code: -32603
data:
code: -32000
message: "rpc error: code = Unknown desc = cannot query with height in the future; please provide a valid height: invalid height"
[[Prototype]]: Object
message: "Internal JSON-RPC error."

Environment

Browser (Chrome, Safari, etc)

Environment (Other)

No response

[ricmoo]

I’m unfamiliar with that chain, but it seems like the chain or node does not support querying future block heights. Why are you using block heights that don’t exist yet?

It doesn’t surprise me that the backend would throw though, as it cannot possibly tell you the future. :)

[flcoder]

If it's not ethers.js, then it could be metamask. I did determine that it seems to only have to do with cosmos... https://github.com/cosmos/cosmos-sdk/blob/084e129fcf62d47366f398cf1066ed14e29af471/baseapp/abci.go#L614

[flcoder]

Can you at least point me to the code that determines what block number it's going to query when trying to get information from the block chain. Why would it put in a block number from the future, why doesn't it just ask for the latest block number. Is ethers trying to anticipate the next block or something? Does it send latest+1 by default or something? Apparently other chains are more forgiving, it seems to be specific to cosmos. But still, it shouldn't be querying latest+1, it should just query for latest. Other chains may fall back to latest, but not cosmos, it throws so something needs to change.

[ricmoo]

Ethers doesn’t anticipate anything. It just sends the string "latest" along for the ride.

[ricmoo]

(you can always install a debug handler if you want to see more info; provider.on("debug", console.log), but it’s a lot ;))

[flcoder]

Ok, cool, well thanks for that info... today I switched rpc endpoints and haven't had the problem so ethers' github probably isn't the best place for this issue I think, I just didn't have a clue where else to get some feedback. Thanks again.