-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Acquire previously failed transaction set from #5318
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
network as new proposal arrives.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #5318 +/- ##
=======================================
Coverage 78.2% 78.2%
=======================================
Files 790 790
Lines 67740 67741 +1
Branches 8177 8173 -4
=======================================
+ Hits 52956 52965 +9
+ Misses 14784 14776 -8
|
All reactions
Sorry, something went wrong.
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.
There are a couple of places in trigger
where failed_
can be set if the received data is somehow incorrect. It might be worth clearing that data out if that happens. But I suspect that is very unlikely to be the case if we get a trusted proposal with it. Extra checking can be added later. This is a good start as-is.
Sorry, something went wrong.
All reactions
…oposal arrives (#5318) Reset the failure variable.
…oposal arrives (XRPLF#5318) Reset the failure variable.
ximinez
bthomee
vlntb
vvysokikh1
Successfully merging this pull request may close these issues.
network as new proposal arrives.
High Level Overview of Change
Clear failure flag to ensure that previously-failed inbound ledger gets acquired if a new trusted proposal arrives.
Context of Change
Type of Change
.gitignore
, formatting, dropping support for older tooling)API Impact
libxrpl
change (any change that may affectlibxrpl
or dependents oflibxrpl
)