-
Notifications
You must be signed in to change notification settings - Fork 332
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
Invalid Utf-8 on Collecting Events on Block that have EVM transaction on Cosmos chain #4007
Comments
Are you able to reproduce this on latest Hermes (v1.8.3) using |
@romac Hi my man, i just update the log. Please check it, thanks for your response. |
Thanks! Can you please share your config for that chain as well? |
The logs you've graciously shared seem to be a little bit garbled and truncated, making it hard to make sense of them. Can you please see if you can get a bigger portion of them, potentially showing multiple errors? 🙏 |
i just update the hermes config @romac. For more information, I have try address_type as evmos but actually it does not work because it does not match signing mechanism of Oraichain, i think address_type is not a problem |
Hi. here is full log. Show log
|
@romac it is too long so i write it down here. Btw, thanks for your response |
Thanks! Can you please re-add the |
Updated log: Show log
|
@romac i just update it, please check it |
Thanks! |
I think I see where the problem comes from, we will take a closer look and work on a fix. Will keep you posted. |
Thank you |
Alright, so we actually already have a fix for this on In the meantime, you can try building Hermes from source and see if it indeed fixes the issue. |
@romac thank you, i will try it ^ ^. If it works then i will close this issue |
@romac Seem like the error is fixed, i will close this. I will open if any error comes up ^ ^. Thanks for your time!. Can I ask more about how the error can be fixed ? I have debug on that error but I does not find a way to fix it ^ ^, is it rooted from tendermint-rs 0.34.0 ^ ^ which is updated to 0.36.0 on master branch |
Yes exactly. Here is the relevant tendermint-rs PR: informalsystems/tendermint-rs#1405 |
Thank you! up to now, everything is fine |
@romac hello, i realize a problem on this version |
|
i believe that the error may be come up from some endpoints you have changed on this version like get_sync or sth which is not implemented on oraibtc-testnet-1 |
@romac i just realize that my chain oraibtc-testnet-1 does not implement get_sync on chain_grpc_status which seem a new feature on master to check whether the chain is syncing or not ^ ^. Seem like it is a good feature, but can i remove it ?. (is there anything will go wrong when i remove check sync on grpc ^ ^) Maybe i have to do it on fork version ^ ^ |
because it is not related on the error, so i should not open it again. But i need a check from you ^ ^ @romac. Many Thanks! |
Summary of Bug
2024-05-29T16:47:45.064828Z ERROR ThreadId(38) event_source.rpc{chain.id=Oraichain}: failed to collect events: RPC error: serde parse error: invalid utf-8 sequence of 1 bytes from index 43 at line 1 column 66308 height=22513078
Version
v1.7.4
Steps to Reproduce
Acceptance Criteria
The text was updated successfully, but these errors were encountered: