-
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
simapp does not support /cosmos.tx.v1beta1.Service/Simulate anymore #12466
Comments
So that line goes to the following: return sdkerrors.QueryResult(sdkerrors.Wrap(sdkerrors.ErrUnknownRequest, "unknown query path"), app.trace) Which makes sense and it seems to me like this should not even be hitting that It should be captured by: // handle gRPC routes first rather than calling splitPath because '/' characters
// are used as part of gRPC paths
if grpcHandler := app.grpcQueryRouter.Route(req.Path); grpcHandler != nil {
return app.handleQueryGRPC(grpcHandler, req)
} In the same method actually. |
It seems like the simulate endpoint was not registered into the grpcQueryRouter. Which is weird, because it should be. @webmaster128 Did you test this with rc1 too? Was this introduced in rc2? |
I could not test rc1 as it would require us to get a Tendermint 0.35 client. That is possible but would be heavy lifting for debugging this. |
I'm observing the same error as above for |
@AmauryM does |
I now tested interchainio/simapp:v0.46.0-rc1 with a Tendermint 0.35 client. This does not contain the issue. |
Should be fixed by #12509 |
I'm testing simapp 0.46.0-rc2 right now in the ComsJS CI system. This seems to work well overall. However, I cannot send simpulate queries anymore (works with 0.42/0.44):
The query path that I can debug in my test case is
/cosmos.tx.v1beta1.Service/Simulate
. Other queries like e.g./cosmos.auth.v1beta1.Query/Account
work without an issue.For historic reasons CosmJS queries through Tendermint RPC. This could change to grpc-web at some point but we are not there yet.
The text was updated successfully, but these errors were encountered: