-
Notifications
You must be signed in to change notification settings - Fork 182
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
Send of Atom modal doesnt update once the transaction has completed #7777
Comments
@MBMaria can you try and confirm this again on your end? Cosmos tx handing in unchained was completely broken at one point and thinking this was the cause, but not sure if this was seen after that fix. I just tested on my end and saw the confirmation right away: |
hi @kaladinlight I'm still experiencing this. using a chrome incognito tab just now. |
I have seen it as well, seems like the websockets degrade the longer they are up. Tried to push a small change and some additional debug logs to try and track things down more. |
Changes look to have made a difference. Seeing detected transaction all through yesterday afternoon and again this morning. Can you give another spot check on your end @MBMaria please 🙏 |
Damnit, just checked again and no update. So that means the websockets are just stopping sending data on the node side of things while technically staying alive so we don't trigger a reconnect. I have a couple more thoughts and will hopefully get to the the bottom of this soon. |
Ok, most recent ws durability improvements look to be working. Going to close this at this time. If there are more issues or instances, would like to open up a fresh ticket to start looking into again. |
Overview
When doing a send of Atom the send modal stays on waiting for confirmation and doesn't change to Success once the transaction has completed
References and additional details
https://jam.dev/c/f8ffb575-0bc0-4895-af4b-10a923ac6bd3
Acceptance Criteria
Modal should update once send has completed
Need By Date
No response
Screenshots/Mockups
No response
Ownership
Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters
The text was updated successfully, but these errors were encountered: