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
If I replace the arch by my own computer it success:
The error we're facing is due to a type conflict between two dependencies of the Cosmos SDK, specifically between cosmossdk.io/core/store and cosmossdk.io/store/types. It seems that there are changes in the KVStoreService API that are not compatible with the code we're using.
Context:
This happened me when I scaffold a v0.50 chain with last version of Ignite, add WASM module (I didn't try without it) and try to build the linux/amd64 release.
I'm running a darwin/arm64 computer (M1)
Describe the Bug:
Ignite build command doesn't produce a linux release from a darwin/arm64 arch.
Steps to Reproduce:
Scaffold a demo chain
Add wasm module
Run: ignite chain build --release -t amd:arm64 from an Apple M1 computer
Environment Details:
**OS:**M1 Darwin Kernel Version 23.4.0
Ignite Version: v28.5.1
Go Version: go version go1.23.1 darwin/arm64
Notes:
The text was updated successfully, but these errors were encountered:
Building a
linux:amd64
orlinux:arm64
releases I get this error:If I replace the arch by my own computer it success:
The error we're facing is due to a type conflict between two dependencies of the Cosmos SDK, specifically between cosmossdk.io/core/store and cosmossdk.io/store/types. It seems that there are changes in the KVStoreService API that are not compatible with the code we're using.
Context:
This happened me when I scaffold a v0.50 chain with last version of Ignite, add WASM module (I didn't try without it) and try to build the linux/amd64 release.
I'm running a darwin/arm64 computer (M1)
Describe the Bug:
Ignite build command doesn't produce a linux release from a darwin/arm64 arch.
Steps to Reproduce:
ignite chain build --release -t amd:arm64
from an Apple M1 computerEnvironment Details:
Notes:
The text was updated successfully, but these errors were encountered: