-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Transactions getting stuck in the "approved" state #4343
Comments
We previously thought we had addressed this in #4086. |
This issue is also presented by users in #3942. |
This could be considered a re-opening of #4086, because we have recent reports of this happening. |
People getting frustrated over this bug: |
so this is most likely related to our mutex getting taken and not released there could be other causes of the issue out there, but this is definitely one |
Does that fix work well cherry-picked on its own? Would be great to get it shipped sooner than we might want to ship the provider rewrite. |
May fix #4343 and related issues, where an error could leave transactions stranded in the approved state.
* Add beginning of test * Resubmit approved transactions on new block May fix #4343 and related issues, where an error could leave transactions stranded in the approved state. * Remove unused test * Re-approve transactions when retrying approved * Add retry approved test * Include approved in pending tx count * Fix getPendingTxs() * Linted * Only throw hash error in submitted state * Only check submitted txs for block inclusion * Fix test expectations
Approved is the state just before "submitted", which should basically be invisible, because we should submit instantly and reliably. Many users have reported (and I have also experienced) a condition where transactions fall into the "Approved" state, and never progress from there.
This was a previous issue, but I can't find it, so I am creating this to track the issue in the meanwhile.
We should ensure that "approved" transactions are re-tried at least some number of times, and then marked as "failed". Other solutions are welcome.
Somewhat mitigated by #3771.
The text was updated successfully, but these errors were encountered: