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

fix: Cosmos SDK 0.47.3 fixes #428

Merged
merged 7 commits into from
Jul 4, 2023
Merged

Conversation

dib542
Copy link
Collaborator

@dib542 dib542 commented Jul 4, 2023

This PR fixes two issues:

  • when running the chain in Docker the REST API was inaccessible
    • this was due to the default Cosmos app config (app.toml settings) specifying localhost in the new version instead of the previous version which specified 0.0.0.0
  • when the REST API was accessible, all Msgs and queries threw a 500 internal server error response with the message:
failed to load state at height 123; version does not exist (latest height: 123)

where the height number was the current block number (which keeps increasing as the chain was still progressing)


The solution to the "failed to load state" error was found by searching the error which lead to the issue and PR:

@@ -188,3 +188,6 @@ require (
)

replace github.com/cosmos/ibc-go/v7 => github.com/Stride-Labs/ibc-go/v7 v7.1.1-0.20230622125415-f45876a168a0

// downgrade of goleveldb to avoid issues: see https://github.com/cosmos/cosmos-sdk/issues/14949
replace github.com/syndtr/goleveldb => github.com/syndtr/goleveldb v1.0.1-0.20210819022825-2ae1ddf74ef7
Copy link
Contributor

Choose a reason for hiding this comment

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

Good call.

@teddyknox teddyknox merged commit 6304fa1 into main Jul 4, 2023
@teddyknox teddyknox deleted the dib542/cosmos-sdk-0-47-3-docker-fixes branch July 4, 2023 16:24
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