You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When you start with a clean Ignite v0.28.3 App and try to add wasm module using a software upgrade you get this error: SetIndex requires index to not be set
The error ‘SetIndex requires index to not be set’ indicates that the index is already set when trying to set it again. This usually happens in the context of index initialisation in the IBC capability module.
To reproduce
Steps to reproduce the behavior:
Scaffold a new v0.28.3 chain with: ignite s chain ignite-wasm
Run it and create an upgrade software proposal. Vote it
Add wasm module to the same using the ignite wasm add command.
Ignite CLI version: v28.3.0
Ignite CLI build date: 2024-03-20T15:31:07Z
Ignite CLI source hash: 159abdca88605ed82cb4aabd52618db91069b7af
Ignite CLI config version: v1
Cosmos SDK version: v0.50.5
Your OS: darwin
Your arch: amd64
Your Node.js version: v20.11.1
Your go version: go version go1.22.1 darwin/arm64
Your uname -a: Darwin iMac-de-Raul.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:41 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8103 x86_64
Your cwd: /Users/xxxx/SDK/ignite_wasm/ignite-wasm
Is on Gitpod: false
The text was updated successfully, but these errors were encountered:
Describe the bug
When you start with a clean Ignite v0.28.3 App and try to add
wasm
module using a software upgrade you get this error:SetIndex requires index to not be set
The error ‘SetIndex requires index to not be set’ indicates that the index is already set when trying to set it again. This usually happens in the context of index initialisation in the IBC capability module.
To reproduce
Steps to reproduce the behavior:
ignite s chain ignite-wasm
wasm
module to the same using theignite wasm add
command.Here are the previous steps:
RaulBernal/ignite-wasm@v1.0.0...v2.0.0
What version are you using?
The text was updated successfully, but these errors were encountered: