bug(optional): ignite cosmosclient
Reecepbcups opened this issue · 2 comments
solution:
pretty sure this is just a cometbft patch version bump issue (i.e. ignite uses cometbft 0.38.A while spawn uses 0.38.B cometbft or something).
Need to check if this is the case for v0.50.1 or off main. ideally matching versions should fix it?
from discord:
https://discord.com/channels/669268347736686612/1242222940167081994
https://pkg.go.dev/github.com/ignite/cli/v28@v28.4.0
Hi i am trying to create a go client, using Ignites cosmosclient, for my chain created with spawn. I had already created the working client for a chain that was extended from chain-minimal. I tried to use my new chain created with spawn (that provides the same functionality, so I thought I could just swap it out), but I ran into some errors I can't seem to resolve.
lc git:(main) ✗ go run main.go
# github.com/cosmos/cosmos-sdk/types
../../../../../go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.50.5/types/context.go:65:29: undefined: comet.BlockInfo
../../../../../go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.50.5/types/context.go:92:36: undefined: comet.BlockInfo
../../../../../go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.50.5/types/context.go:300:48: undefined: comet.BlockInfo
It seems to be dependency errors. I tried to fix these by changing some things locally in that package, but that induces a bunch of new dependency errors. Does anyone know how I can fix this?
Thanks
i’ve seen this before with weird cometbft cosmossdk stuff so i assume It’s that, in which we can’t do anything & can be closed
not an issue yea it was the core module being improperly tagged with v0.50
responsed to them