Skip to content
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

gm parse errors with v0.43 gaia build #1312

Closed
5 tasks
colin-axner opened this issue Aug 30, 2021 · 1 comment · Fixed by #1331
Closed
5 tasks

gm parse errors with v0.43 gaia build #1312

colin-axner opened this issue Aug 30, 2021 · 1 comment · Fixed by #1331
Assignees
Labels
I: infrastructure Internal: related to Infrastructure (testing, deployment, etc)
Milestone

Comments

@colin-axner
Copy link
Contributor

colin-axner commented Aug 30, 2021

Crate

gm

Summary of Bug

When using the upcoming build of gaia which bumps SDK to v0.43, gm returns parsing errors when integrating with hermes. gm hermes config and gm hermes keys are both affected

Version

I tried with latest commit on master c518e15 and v0.7.0.

Steps to Reproduce

  1. Set one chain in gm.toml to use the binary linked above.
  2. Start the chains
  3. Run gm hermes config
gm hermes config
While parsing config: unexpected end of JSON input
  1. Run gm hermes keys (after fixing config file by adding second chain)
gm hermes keys
Success: Added key 'wallet' (cosmos1hjr37fjjqxke3rudceuj90gsmqvnqy2jjjz29a) on chain network1
Error: 
   0: error encoding key
   1: EOF while parsing a value at line 1 column 0

Location:
   /home/bartleby/.cargo/registry/src/github.com-1ecc6299db9ec823/flex-error-0.4.2/src/tracer_impl/eyre.rs:31

Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Acceptance Criteria

gm works with the above linked build

Notes

I noticed when running gm start, v5 gaia binaries don't print any extra information, but the new binary for v0.43 does:

gm start
Creating network1 config...
network1 started, PID: 91491, LOG: /home/bartleby/.gm/network1/log
Creating network2 config...
{"name":"validator","type":"local","address":"cosmos1mryhmlxry4yrc6alq3jz9n7h29s45jddkxmqac","pubkey":"{\"@type\":\"/cosmos.crypto.secp256k1.PubKey\",\"key\":\"AuCpRwf2873W/nO0T4k9xX/PmXKEiG75OlSWfcpUrWEF\"}","mnemonic":"educate other loud prison brown only board public train predict little useful lift lucky coil shell drill wise film moment want diary economy ocean"}
{"name":"wallet","type":"local","address":"cosmos1jn6h63d4y36m0flt6thhcywu2neqhuar8l85hc","pubkey":"{\"@type\":\"/cosmos.crypto.secp256k1.PubKey\",\"key\":\"AjkIklfuTuf+wno7kFL+Td+cjAI18g7Hvs/H0uFqSy93\"}","mnemonic":"sweet impose march today wire behave primary critic fence invite fossil split blame seminar fiction shuffle diamond observe video target ecology wait chimney envelope"}
network2 started, PID: 92014, LOG: /home/bartleby/.gm/network2/log

gm starts the chains just fine. The odd part is I tested similar binaries during the v0.43 beta phase and everything worked fine, so it must be due to some recent change, maybe during the rc release cycle.

It is possible there is an issue with the gaia binary

Edit: Manually restoring the keys with hermes using the outputs from creating the chain worked


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@colin-axner
Copy link
Contributor Author

as a side note, I think the default rpc_timeout should be bumped from 1s to something higher (I usually need to change this everytime)

@adizere adizere mentioned this issue Sep 7, 2021
10 tasks
@greg-szabo greg-szabo self-assigned this Sep 7, 2021
@adizere adizere added this to the 09.2021 milestone Sep 9, 2021
@adizere adizere added the I: infrastructure Internal: related to Infrastructure (testing, deployment, etc) label Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: infrastructure Internal: related to Infrastructure (testing, deployment, etc)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants