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

v8.0.x cleanups #2077

Closed
wants to merge 12 commits into from
Closed

v8.0.x cleanups #2077

wants to merge 12 commits into from

Conversation

faddat
Copy link
Contributor

@faddat faddat commented Jan 25, 2023

This PR:

  • updates to sdk v0.45.12
  • adds replaces from cosmos-sdk repository
  • adds the fast node flag, default is fastnodedisable=true, same as sdk upstream

@faddat faddat reopened this Jan 25, 2023
@faddat faddat changed the title Use go 1.19 for gaia v8.0.x v8.0.x cleanups Jan 25, 2023
@mpoke
Copy link
Contributor

mpoke commented Jan 25, 2023

Note that SDK 0.45.12 still uses go 1.18. Thus, we should not update to go 1.19.

@faddat
Copy link
Contributor Author

faddat commented Jan 26, 2023

@mpoke If we use 1.18 then it is possible for validators to have mixed binaries.

If we use 1.19 then it is impossible for validators to have mixed binaries. We studied this at osmosis. 1.19 good. 1.18 good. Mixed bad.

Thus 1.19

@faddat
Copy link
Contributor Author

faddat commented Jan 26, 2023

@mpoke I've reverted to 1.18 -- please know that I do not recommend this, and urge that we use 1.19.

Note: cosmos-sdk team recommends taking measures to ensure that we use only one version of go across the validator set:

When we did this at Osmosis, we used Makefile + 1.18 -- however, after testing, and after a few validators having 1.19 related explosions because they install the chain in the logical manner, eg:

go install ./...

the go version was bumped to 1.19 because otherwise (present continuous verb) validators like myself will run into problems.

There is no need to lower our go runtime version to match the SDK's, life is great with the higher one. The only thing we need to do is be at 1.18+. And... 1.18 puts validators into pickles.

@sonarcloud
Copy link

sonarcloud bot commented Jan 26, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

// TODO Remove it: https://github.com/cosmos/cosmos-sdk/issues/10409
github.com/gin-gonic/gin => github.com/gin-gonic/gin v1.8.1

// use cosmos style protobufs
github.com/gogo/protobuf => github.com/regen-network/protobuf v1.3.3-alpha.regen.1

github.com/jhump/protoreflect => github.com/jhump/protoreflect v1.9.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @faddat , where this is used ? and why we want v1.9.0 ? Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I slavishly follow upstream recommendations, and that's recommended in the sdk.

@github-advanced-security
Copy link

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

@faddat
Copy link
Contributor Author

faddat commented Apr 29, 2023

Will return to this after we've got 47 in the main branch, but closing for now.

@faddat faddat closed this Apr 29, 2023
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 this pull request may close these issues.

3 participants