-
Notifications
You must be signed in to change notification settings - Fork 331
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
Event changes in TM v0.37 #1353
Comments
I am getting the same error with the following stack. same versions as above, using @cosmjs 0.29.5
|
cc @@pyramation |
Should we do this ourself, its a blocker for a variety of things |
This particular change was already implemented in the Tendermint 0.35 client last summer. If I understand things correctly, only 0.34 and 0.37 are needed now. So we can rename the 0.35 client to 0.37 and test it against a 0.37 backend. |
Is there a better source for Tendermint 0.37 docker images than |
I believe it's there https://hub.docker.com/r/cometbft/cometbft/tags/ |
What do you currently need this client for? I think the standalone client is ready and I can create a StargateClient/CosmWasmClient constructor where you pass an explicit tendermint client (either 34 or 37). The auto-detection would be a bigger thing as the functionality was removed at some point. I don't want to block the client on the auto-detection. Does this make sense? |
#1376 is ready for anyone wants to review it |
@webmaster128 maybe I am missing something here, but i am running cosmos-sdk simd
CometBFT version With
My issue is even though there is an error and server returns 500, some of the times the txn seems to go through and the faucet seems to transfer the tokens. Am I missing something? PS. This could just be limited to the Faucet. Please let me know if there is a better place to have this discussion. |
Actually you can see this in the gist of the logs during initialization itself... Error statement during refil, but refil actually happens https://gist.github.com/Anmol1696/60b3e851b66fe6d45674dea9b4f92081#file-logs-txt Maybe it is still some old validatation of address? |
@Anmol1696 you need a pre-release of 0.31 to get the Tendermint 0.37 client by default |
Ahh yes worked like a charm. |
0.30 ships a standalone Tendermint 0.37 client that you can use manually. From 0.31 onwards we have auto-detection in higher level clients and use it by default under the hood. Fianal release very very soon. |
Error re-occurs for cosmos-sdk version 50 as well. Does support for TM 0.38 also need some changes? I am using cosmjs-facuet for running simd nodes with Starship. It would be nice if cosmos-sdk can be tested with cosmjs (but hard to do if there are too many breaking changes). |
High level clients use the Tendermint 0.34 client as a fall back when they find a version that does not start with "0.37". This might explain the problem. Could you open a ticket for Tendermint 0.38 / Cosmos SDK 0.50 support? |
This idea has been around for a while but CosmJS does not have the necessary development resources to keep up with Cosmos SDK development. Trying to test Cosmos SDK with an independent re-implementation creates dependency cycles that are very hard to maintain. |
The SDK v0.47 upgrades TM to v0.37, which re-surface cosmos/cosmos-sdk#11997.
According to cosmos/cosmos-sdk#11997 (comment), there is already a TM v0.35 client.
It would be helpful if there is a cosmjs version supporting the event changes in v0.37 (ref: https://github.com/tendermint/tendermint/blob/main/UPGRADING.md#unreleased)
The text was updated successfully, but these errors were encountered: