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
When trying to query anything with a --height that is pruned, the response is an error with codespace "sdk" and code 18 ("invalid request") as seen in e.g. Agoric/agoric-sdk#9033 . This is the same code as is used for responding to a proof-covered query when height <= 1, but unlike that case, the client's request is not invalid—rather, it is unserviceable due to server-side state that is not known a priori. As such, the response should indicate that difference by not reusing the code.
Looking at types/errors/errors.go, code 38 ("not found") or possibly code 26 ("invalid height") would seem more appropriate (but of the two, I much prefer "not found" because "invalid height" is already used for request height > lastBlockHeight, which like height <= 1 is actually a problem on the client side.
Cosmos SDK Version
0.50.5, main
How to reproduce?
Query a node with --height <pruned_height_number> for a pruned block.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What happened?
When trying to query anything with a
--height
that is pruned, the response is an error with codespace "sdk" and code 18 ("invalid request") as seen in e.g. Agoric/agoric-sdk#9033 . This is the same code as is used for responding to a proof-covered query when height <= 1, but unlike that case, the client's request is not invalid—rather, it is unserviceable due to server-side state that is not known a priori. As such, the response should indicate that difference by not reusing the code.Looking at types/errors/errors.go, code 38 ("not found") or possibly code 26 ("invalid height") would seem more appropriate (but of the two, I much prefer "not found" because "invalid height" is already used for request height > lastBlockHeight, which like height <= 1 is actually a problem on the client side.
Cosmos SDK Version
0.50.5, main
How to reproduce?
Query a node with
--height <pruned_height_number>
for a pruned block.The text was updated successfully, but these errors were encountered: