-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account Query Failure #7007
Comments
Maybe (1) is expected because we haven't finished some sort of client migration or something...idk? But (2) should be addressed for sure. |
Hmm... I imagine this is because we are in the middle of enabling proto JSON and disabling amino JSON. Integration tests now use proto but the binaries still use amino. That switch will be flipped after #6859 is merged. I split it into 3 PRs to make review easy. Sorry for the janky transition. |
Will close this after those PR(s) are merged then. |
We need to check and see if that fixed it. There could be something else. @sahith-narahari ? |
Now I can't even start a network...
(mental note to self: Sigh...I think we need to bring back the localnet bash script) |
Looks like the query account is still failing, I added a test here for the same #6973 |
I would first look into making sure we can actually start a network... |
How hard do you think it would be to bring back some of the out of process integration tests for critical commands? We don't need all the module tests out of process - maybe just |
I was thinking just brining back the |
IMHO: the issue here is the missing interface implementation. The address in the response is of type
and a fix is likely:
|
Which issue @alpe? There are three currently:
|
Sorry for the confusion, I came from #7034. I have not looked into the other problems. |
That's exactly the fix thanks @alpe ! I am working on addressing all 3. |
A fix for 2 and 3 is in #6973 |
Summary of Bug
$ simd q account cosmos1xg5ahw8r8vwgzjh6uwamszkzx06ndkpk2fnvk5 --chain-id=$CHAIN_ID Error: internal
Version
master as of
1744194e7
Steps to Reproduce
For Admin Use
The text was updated successfully, but these errors were encountered: