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

Account sequence takes a while to update for some chains #1805

Open
luciorubeens opened this issue May 13, 2022 · 2 comments
Open

Account sequence takes a while to update for some chains #1805

luciorubeens opened this issue May 13, 2022 · 2 comments
Labels
bug P? Bug without impact estimated

Comments

@luciorubeens
Copy link
Contributor

Describe the bug

The response from the /chain/osmosis/numbers/<keyhash> endpoint is not updated immediately, especially notable when sending a multi-hop swap on osmosis.

CleanShot 2022-05-12 at 21 50 09

To Reproduce
Steps to reproduce the behavior:

Try to make a swap immediately after another on osmosis chain.

Solution

A workaround could be to retry if it returns this code error.

@luciorubeens luciorubeens added the bug P? Bug without impact estimated label May 13, 2022
@faboweb
Copy link
Contributor

faboweb commented May 13, 2022

@EmerisHQ/emeris-backend

@Pitasi
Copy link

Pitasi commented May 13, 2022

Adding some context:

The /chain/osmosis/numbers/<keyhash> endpoint hits the chain nodes directly using RPC and returns the result. I'm pretty sure this endpoint is cached by nginx for 2 seconds so we might want to take this into account as well.

I think the delay you are seeing could be because our nodes takes a while to sync between each other (e.g. the transaction was made to node X and you are asking numbers to node Y, but you need to wait some seconds for node Y to be in sync).
I'm not sure if there's much we can do here, nothing "easy" comes to my mind 😕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug P? Bug without impact estimated
Projects
None yet
Development

No branches or pull requests

3 participants