-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Bug]: Querying cosmos-sdk native modules without --node flag #20689
Comments
I've set up my node in config.toml to serve at rpc I'm using |
I see, yes we fixed the bug on release/v0.50.x (#19060) but haven't tagged a the next version of client/v2 just yet (#19530). Still blocked on one PR of mine to proceed. I would suggest if pressing to use |
Thanks for the quick responses, I've tested it with the suggested client/v2 version and it works as expected! |
Is there an existing issue for this?
What happened?
On a chain which has upgraded to cosmos-sdk v0.50+ if you try to query a native cosmos-sdk module without using the
--node
flag, the node serves responses only onlocalhost:26657
, no matter what configuration is set.For example:
gaiad query gov params
returns:Error: post failed: Post "http://localhost:26657": dial tcp 127.0.0.1:26657: connect: connection refuse
The
localhost:26657
value is taken from client/config/config.go func DefaultConfig()I suspect this problems is connected to the new AutoCLI feature.
Cosmos SDK Version
0.50+
How to reproduce?
Run
binary query gov params
on a node with sdk v0.50+The text was updated successfully, but these errors were encountered: