relayer configure error when going through the IBC basics tutorial

[fadeev]

~/planet ignite relayer configure -a \
  --source-rpc "http://0.0.0.0:26657" \
  --source-faucet "http://0.0.0.0:4500" \
  --source-port "blog" \
  --source-version "blog-1" \
  --source-gasprice "0.0000025stake" \
  --source-prefix "cosmos" \
  --source-gaslimit 300000 \
  --target-rpc "http://0.0.0.0:26659" \
  --target-faucet "http://0.0.0.0:4501" \
  --target-port "blog" \
  --target-version "blog-1" \
  --target-gasprice "0.0000025stake" \
  --target-prefix "cosmos" \
  --target-gaslimit 300000
------
Setting up chains
------

? Source Account default
? Target Account default

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x38 pc=0x1053bcfc0]

goroutine 1 [running]:
github.com/ignite/cli/ignite/pkg/cosmosaccount.Account.Address({{0x0?, 0x5?}, {0x0?, 0x0?}}, {0x16b2235de, 0x6})
        /home/runner/work/cli/cli/go/src/github.com/ignite/cli/ignite/pkg/cosmosaccount/cosmosaccount.go:136 +0x30
github.com/ignite/cli/ignite/cmd.initChain(0x14000ed0f00, {{{0x14000668660, 0x1e}, {0x105debc67, 0x6}, {0x105de5813, 0x4}, {0x106ff3930, 0x14000513400}}}, {{0x14000522540, ...}, ...}, ...)
        /home/runner/work/cli/cli/go/src/github.com/ignite/cli/ignite/cmd/relayer_configure.go:482 +0x2b4
github.com/ignite/cli/ignite/cmd.relayerConfigureHandler(0x14000ed0f00?, {0x105de4d9b?, 0x1d?, 0x1e?})
        /home/runner/work/cli/cli/go/src/github.com/ignite/cli/ignite/cmd/relayer_configure.go:386 +0x3354
github.com/spf13/cobra.(*Command).execute(0x14000ed0f00, {0x14000ee05a0, 0x1d, 0x1e})
        /home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:856 +0x4c4
github.com/spf13/cobra.(*Command).ExecuteC(0x14000ea4000)
        /home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:974 +0x354
github.com/spf13/cobra.(*Command).Execute(...)
        /home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:902
github.com/spf13/cobra.(*Command).ExecuteContext(...)
        /home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:895
main.main()
        /home/runner/work/cli/cli/go/src/github.com/ignite/cli/ignite/cmd/ignite/main.go:17 +0x7c

~ ignite version
Ignite CLI version:	v0.23.0
Ignite CLI build date:	2022-07-24T18:17:44Z
Ignite CLI source hash:	64df9aef958b3e8bc04b40d9feeb03426075ea89
Your OS:		darwin
Your arch:		arm64
Your go version:	go version go1.18.3 darwin/arm64
Your uname -a:		Darwin Deniss-MBP 22.0.0 Darwin Kernel Version 22.0.0: Wed Jul 20 01:53:56 PDT 2022; root:xnu-8792.0.188.141.3~2/RELEASE_ARM64_T6000 arm64
Your cwd:		/Users/fadeev
Is on Gitpod:		false

I understand Ignite will soon be updated to v0.46, but I think it's crucially important to specify the version of Ignite that was used when testing a tutorial. Somewhere between v0.19 and v0.23 something happened that may have broken the relayer.

[fadeev]

We also have a very old issue about this as well #1820

Maybe this has something to do with the OS, not the relayer.

[jeronimoalbi]

The runtime error happens because an error is returned as nil in v0.23.0. The issue was spotted and fixed in #2664 by a contributor but it came after the release of v0.23.0.

@ilgooz should a v0.23.1 be released to fix the issue?

After reproducing it locally with v0.23.0 and the nil error fixed I got the actual error:

Bytes left over in UnmarshalBinaryLengthPrefixed, should read 10 more bytes but have 154

I am not sure but I think the issue is that my keyring was migrated to work with the upcoming release and once the keyring is updated it is not backwards compatible. @fadeev did you by chance have run the current develop version before running the v0.23.0 for the tutorial?

cc @aljo242

[fadeev]

did you by chance have run the current develop version before running the v0.23.0 for the tutorial?

I did, yes.

[jeronimoalbi]

This issue happens when running the v0.23.0 or lower version after running the current develop version (upcoming v0.24.0) because the keyring is updated automatically as part of #2756 and once that happens the changes are not backwards compatible.

[fadeev]

Thanks for clarifying this, @jeronimoalbi 👍