-
Notifications
You must be signed in to change notification settings - Fork 81
Conversation
Ok thanks by your support ;) |
thanks for the state sync script that saved more hours of my life than I can even estimate. |
This PR will remove starport's cmd folder shims, and leave the chain otherwise compatible with the nightly build of starport. Then we can do one that adds the lsm. |
Hi there, ignite-hq shouldn't be used any more, it's the previous org. To get the latest ignite CLI, it's a little tricky for the moment : you can't
|
thanks! |
@tbruyelle what is "GOSUMDB=off" haven't seen this before. |
That disables the checksum verification with sum.golang.org. For some reason, it doesn't work with our latest version (sum.golang.org returns a 404 not found). It might also be related to this CI is passing now 🎉 |
Where is the state sync script? |
Do you mean this? |
testutil/network/network.go
Outdated
"github.com/cosmos/cosmos-sdk/testutil/network" | ||
sdk "github.com/cosmos/cosmos-sdk/types" | ||
authtypes "github.com/cosmos/cosmos-sdk/x/auth/types" | ||
"github.com/ignite/cli/ignite/pkg/cosmoscmd" | ||
"github.com/jaekwon/testify/require" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this was intended or not, but since this looks pretty abandoned I would perhaps suggest using github.com/stretchr/testify
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That came in with the updated ignite cli code.... let's see if the alternative works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my first inclination was to remove ignite altogether.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we removed Ignite CLI - was causing problems in CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we removed Ignite CLI - was causing problems in CI.
Before remove it:
- How to reproduce the problems?
- Should be fixed in github.com/ignite/cli v0.24.0
I have opened a new branch here
main...SDK-v0.46.1-&-IBC/go-v5-on-the-way
- ICA integration fixed
- IBC production version 5
Please fell free to collaborate there 🙏
@faddat we have just integrated the ICA in our main (production) branch, so this development should also contains it. Thanks 😊 |
go.mod
Outdated
github.com/grpc-ecosystem/grpc-gateway v1.16.0 | ||
github.com/ignite/cli v0.23.0 | ||
github.com/ignite/cli v0.23.1-0.20220902151340-d0fd60f1d4ad | ||
github.com/jaekwon/testify v1.6.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here. I also see that github.com/stretchr/testify is already included, so probably not necessary with this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the review!
I think that the ignite cli uses the jaekwon code. Both imports came in when updating the ignite cli, and I believe came from upstream.
@bjaanes thanks very much for the review! I've addressed your findings here, and that was quite helpful. |
@robert-zaremba also on just about every cosmos chain of a certain age. Gaia def has it, I did significant refactors, but it is fundamentally from here. |
Your code run smooth as I tested in a new dev-chain :D |
Question @faddat Should we bump Tendermint to v0.35.x? I think yes |
@faddat I have compiled your code and works flawless :) Migrations to ibc-go v4 and v5 appears to be trivial; look: |
No, tendermint v0.35 is retracted. |
Re IBC v5: important decision is if you want to enable ICA and IBC fees. |
Full integration of ICA here. (and new stable production version IBC/go v5.0): also for you @faddat @bjaanes @tbruyelle
Or:
For this and for other issue the IBC Team relased the security version. |
Definitely we decided to close this PR in favor to develop the branch https://github.com/BitCannaGlobal/bcna/tree/SDK_046 |
Thanks for the report, I created an issue in CLI ignite/cli#2867. Why do you say we need to disable it ? |
I'm curious too to know @robert-zaremba and @faddat commented it before |
whole thing needs a refactor, will do soon.... |
Certainly it needs because I refactored the branch v1.4.X & v1.5.X based in:
I planed to do next week but maybe before if I can. Anyway you can work in https://github.com/BitCannaGlobal/bcna/tree/SDK_046 |
BTW, the ICA controller stack is going to be updated in IBC v6. |
AS for Ignite CLI - we had problems with it in CI and eventually just removed it because nobody was using it. |
In our next upgrade (next monday) we will include the ICA stack (with controller = disabled) in the v0.45 branch. By the moment is not our business enable it. Next upgrade will be v0.46 and IBC/5 or 6 Many thanks by your advice 🙏 |
Attending your past comments and @faddat ones, we have removed Thanks everyone by your support 👏 👏 v0.46 migration is at https://github.com/BitCannaGlobal/bcna/tree/SDK_046 branch :) |
@RaulBernal We removed cosmoscmd from Ignite CLI v0.25.0, here is the complete migration guide for existing chain : https://docs.ignite.com/migration/v0.25.0#removing-cosmoscmd About the ICA controller bug you have raised, there's also a migration guide : https://docs.ignite.com/migration/v0.25.0#fix-ica-controller-keeper-wiring
@robert-zaremba I'm pretty sure that you no longer have the problem with the latest version of CLI, we fixed a couple of dependencies issues. Anyway if you did the effort to remove the CLI dependency from your chain, there's no reason to re-add it :) I just try to clarify for readers. |
Yeah I've participated in that doc with my testing :) really a pleasure work with you (I only get from ignite/cli the openapi package) In next days I'm going to refactor again with all guides. We make COSMOS big with guides. I think I'm going to share a doc integrating the NFT feature in SDK v046 (and Ignite CLI) |
Sure. Thanks for the note @tbruyelle . |
I'll use this branch to bump bcna to v46, mainly as a test/exploration.
....and it's done now.
The next step, which will be in a separate PR, will be the liquid staking module.
opinion: ibc-go v5.0.0 will be out soon, and it likely makes the most sense, to upgrade to 46+lsm. BCNA would be the first to do this, and it would enable the full feature set of quicksilver, while improving performance and making the code here generally easier to work with.
Huge thanks to: