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

Tethys upgrade #68

Closed
wants to merge 63 commits into from
Closed

Tethys upgrade #68

wants to merge 63 commits into from

Conversation

ChristianBorst
Copy link
Collaborator

@ChristianBorst ChristianBorst commented Oct 2, 2024

Features:

  • SDK upgrade to v0.46.16
  • IBC upgrade to v6.3.1
  • Ethermint upgrade to v0.22
  • Group module added
  • Feegrant module added
  • Distribution parameters updated

@ChristianBorst ChristianBorst force-pushed the c/sdk-46-upgrade branch 4 times, most recently from 561c7f4 to f9e73d7 Compare October 7, 2024 19:21
@ChristianBorst ChristianBorst force-pushed the c/sdk-46-upgrade branch 8 times, most recently from 2804ff9 to 3c90f71 Compare November 21, 2024 15:03
@ChristianBorst ChristianBorst changed the title Neutrino upgrade Tethys upgrade Jan 9, 2025
@ChristianBorst ChristianBorst force-pushed the c/sdk-46-upgrade branch 4 times, most recently from af9b9ad to 0ae35df Compare January 12, 2025 21:06
The binary and go testing depends on the solidity folder contents
because we embed contracts for use by the x/erc20 module. To fix the go
CI tasks they must all install node.js and compile the solidity folder
before formatting the output for use by the go files in contracts. After
this the build, lint, and test tasks can all run.

Because they are no longer dependent on the build step, test and lint
are now completely parallel with build.
@ChristianBorst ChristianBorst force-pushed the c/sdk-46-upgrade branch 3 times, most recently from 89a69e1 to 739f992 Compare January 12, 2025 22:53
This test required no error for calling an endpoint that didn't exist.
Behavior wise this wasn't ever correct but previously the failure
occured at a different location in the call. Now it correctly occurs
when we try to call a method that obviously doesn't exist.

Contriburing to this is that calling "" is implicitly the constructor.
So the error was different than it normally would be for a unknown
method.
Since the docker test and the ci test run on different flows now we need
to call this specifically in the ci flow.
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.

2 participants