-
Notifications
You must be signed in to change notification settings - Fork 228
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
Errors parsing the response or Client RPC #10
Comments
@amanusk it's possible the Tendermint RPC API changed to return an integer here rather than a string. If so the code parser needs to be modified... ideally to accept both. |
amanusk
added a commit
to amanusk/tendermint-rs
that referenced
this issue
Aug 14, 2019
Addresses issue informalsystems#10 Added tests for both cases
amanusk
added a commit
to amanusk/tendermint-rs
that referenced
this issue
Aug 14, 2019
Addresses issue informalsystems#10 Added tests for both cases Signed-off-by: amanusk <[email protected]>
amanusk
added a commit
to amanusk/tendermint-rs
that referenced
this issue
Aug 14, 2019
Addresses issue informalsystems#10 Added tests for both cases Signed-off-by: amanusk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to use the client RPC to interact with the basic
abci-cli kvstore
application.I have run
tendermint node
andabci-cli kvstore
from two terminals.RPC calls with curl as in the examples here all work as expected.
To try and broadcast a transaction from rust I use the following code:
I am getting the error
When calling
curl 'localhost:26657/abci_query?path=""&data="abcd"&prove=false'
afterwards, I do get a response where I can see thatabcd
was indeed stored successfully, so the problem is with parsing the response on the client side.From some poking around it seems that this has to do with the
Code
field in the response, perhaps it should be"0"
and not0
.Any help solving this is appreciated. Is this a problem of the RPC documentation?
The text was updated successfully, but these errors were encountered: