search

EmerisHQ / demeris

Emeris web app
https://app.emeris.com/
Apache License 2.0
12 stars 2 forks source link

Txs stay pending even though they succeed #620

Closed akc2267 closed 2 years ago

akc2267 commented 3 years ago

This happens pretty often for me and across multiple chains. Most recently I moved CRO from cosmos-hub to crypto.org chain. The Tx pending screen displayed the warning that the tx was taking longer than usual and would revert in 4min. I refreshed the page and the CRO was already available on crypto.org chain. Emeris somehow missed the tx success update.

clockworkgr commented 3 years ago

This happens pretty often for me and across multiple chains. Most recently I moved CRO from cosmos-hub to crypto.org chain. The Tx pending screen displayed the warning that the tx was taking longer than usual and would revert in 4min. I refreshed the page and the CRO was already available on crypto.org chain. Emeris somehow missed the tx success update.

Need to monitor the requests to the tickets endpoint when this happens. Almost certainly they stay stuck in pending or transit (meaning this is a backend/tickets issue)..

If tickets update correctly, then it is a frontend issue but highly unlikely

nassdonald commented 3 years ago

I can confirm that this is happening to me too, even with a send to address transfer on the same chain. When I check an explorer, the tx has succeeded but the front-end shows the 4-minute revert message (irrelevant for non-IBC txs, right?) and then eventually shows the "Contact support" error state.

gamarin2 commented 3 years ago

I can confirm that this is happening to me too, even with a send to address transfer on the same chain. When I check an explorer, the tx has succeeded but the front-end shows the 4-minute revert message (irrelevant for non-IBC txs, right?) and then eventually shows the "Contact support" error state.

Can you give me a way to replicate? I'm not able to right now

nassdonald commented 3 years ago

I'm sending OSMO from one wallet (Bob) to another (Alice) to test it and it seems that the transfer has gone through successfully while the front-end still thinks it's stuck. Does the 4-minute revert message also apply to non-IBC transfers? I guess it would.

Here's the tx details on Mintscan, showing almost immediately after signing:

Screen Shot 2021-09-18 at 12 48 47
akc2267 commented 3 years ago

Screen Shot 2021-09-21 at 1 05 55 PM Screen Shot 2021-09-21 at 2 48 31 PM Screen Shot 2021-09-21 at 9 18 15 AM

caught this bug happening again a few times. Note this also happens to the Swap confirmation widget. The portfolio asset view updates, showing the correct asset amounts, but the widget gets stuck on tx pending

gamarin2 commented 3 years ago

This is a backend issue (rpcwatcher), not a frontend issue

nassdonald commented 2 years ago

This is still happening and it's a pretty crappy UX. Eventually it times out and users have to view in an explorer to see whether the tx has been successful or not.

gamarin2 commented 2 years ago

@nassdonald we will be refactoring tx observability to make it more reliable.

Also we are soon getting endpoints that will enable us to query the context if things fail instead of pointing to block explorer (which will still be there, but only as a very last resort)

eitjuh commented 2 years ago

Cllosing, resolved by websocket feature