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

New warnings with v1.4.9 #66

Closed
alpe opened this issue May 11, 2023 · 2 comments · Fixed by #67
Closed

New warnings with v1.4.9 #66

alpe opened this issue May 11, 2023 · 2 comments · Fixed by #67
Assignees

Comments

@alpe
Copy link

alpe commented May 11, 2023

The following warnings showed up on any wasmd CLI command. This happened after bumping the version from v1.4.8 to v1.4.9:

WARNING: proto: file "google/protobuf/any.proto" already registered
WARNING: proto: file name query.proto does not start with expected testdata/; please make sure your folder structure matches the proto files fully-qualified names
WARNING: proto: file name testdata.proto does not start with expected testdata/; please make sure your folder structure matches the proto files fully-qualified names
WARNING: proto: file name tx.proto does not start with expected testdata/; please make sure your folder structure matches the proto files fully-qualified names
WARNING: proto: file name unknonwnproto.proto does not start with expected testdata/; please make sure your folder structure matches the proto files fully-qualified names

see https://app.circleci.com/pipelines/github/CosmWasm/wasmd/3516/workflows/b257588d-5951-4476-80b2-ceefbc2cd20f/jobs/14618

These warnings are confusing and were breaking CI scripts that expect a concrete output

@julienrbrt
Copy link
Member

@julienrbrt
Copy link
Member

julienrbrt commented May 11, 2023

The warning will completely disappear with Cosmos SDK v0.47.3 and cosmos/gogoproto v1.4.10.
When on Cosmos SDK v0.47.0-v0.47.2, best to stay on a version < 1.4.9.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants