CosmWasm / CosmWasm/wasmd

panic: proto: could not resolve import

Open
#1,785 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
416
Forks
538
PR merge metrics
No merged PRs in 30d

Description

```
panic: proto: could not resolve import "core/crypto/pb/crypto.proto": not found

goroutine 1 [running]:
github.com/CosmWasm/wasmd/app.NewWasmApp({0x1043356d0, 0x106611700}, {0x104355010, 0x14001188b80}, {0x0, 0x0}, 0x0, {0x1042f1f78, 0x140008a2150}, {0x1400141eb00, ...}, ...)
github.com/CosmWasm/wasmd/app/app.go:903 +0x7378
main.NewRootCmd()
github.com/CosmWasm/wasmd/cmd/wasmd/root.go:40 +0x504
main.main()
github.com/CosmWasm/wasmd/cmd/wasmd/main.go:14 +0x1c
```

commenting out https://github.com/CosmWasm/wasmd/blob/main/app/app.go#L902-L904 works fine.

Steps to reproduce:
* `go mod replace github.com/cosmos/cosmos-sdk => github.com/rollkit/cosmos-sdk v0.50.1-rollkit-v0.11.19-no-fraud-proofs`
* `github.com/rollkit/cosmos-sdk` uses `github.com/rollkit/rollkit`, which in turn uses `go-libp2p` which looks like having the `core/crypto/pb/crypto.proto` that is not found above.
* `make install`
* `wasmd start` throws the error above

Contributor guide

Open the contributing guide

Research direction

Start by applying the reported go.mod replacement, running `make install`, and reproducing the failure with `wasmd start`. Inspect app/app.go at lines 902-904 and trace the reported cosmos-sdk, rollkit, and go-libp2p dependency chain. Done means `wasmd start` no longer panics while resolving `core/crypto/pb/crypto.proto`.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.