-
Notifications
You must be signed in to change notification settings - Fork 524
daemon: pool error messages and old txn expiration #4755
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4755 +/- ##
=======================================
Coverage 54.59% 54.59%
=======================================
Files 414 414
Lines 53665 53665
=======================================
Hits 29297 29297
Misses 21945 21945
Partials 2423 2423 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
jasonpaulos
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable to me
af35e7d to
6606939
Compare
|
ok, removed the statusCache pruning |
jasonpaulos
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is good to take as is. I didn't open a PR for the original issue because I wanted to find a way of testing the change, but I don't think that's worth waiting for.
Summary
Transaction pools might store failed transactions for quite a long time on its StatusCache.
When someone requests a pending transaction and it gets retrieved from the StatusCache,
there is no indication it actually failed. A user might have an impression the txn is fine but stuck.
In order to give a correct feedback, report any errors from the StatusCache via REST API.