Bound sync loops in lightning-transaction-sync#4612
Conversation
|
👋 Thanks for assigning @tnull as a reviewer! |
|
No new issues found. All previously identified problems have been resolved in the current version of the diff:
The only remaining observation (dead upper bound of 100 when 10 is the effective limit) was already posted in a prior review pass. |
9db7e55 to
44c8162
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4612 +/- ##
==========================================
+ Coverage 86.12% 86.43% +0.30%
==========================================
Files 157 158 +1
Lines 108922 109293 +371
Branches 108922 109293 +371
==========================================
+ Hits 93812 94463 +651
+ Misses 12495 12284 -211
+ Partials 2615 2546 -69
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
44c8162 to
bfee825
Compare
If we start syncing from an electrum or esplora server and find that the chain moved during our sync, we reset and start fresh. However, if that happens repeatedly, we probably shouldn't just spin forever. Here we give up after ten attempts and just hope we can sync properly later.
bfee825 to
1c7fcb7
Compare
If we start syncing from an electrum or esplora server and find that the chain moved during our sync, we reset and start fresh. However, if that happens repeatedly, we probably shouldn't just spin forever. Here we give up after ten attempts and just hope we can sync properly later.