-
Notifications
You must be signed in to change notification settings - Fork 404
Cut 0.0.111 #1712
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
Cut 0.0.111 #1712
Conversation
* HTLCs which fail prior to being sent over their first hop are now marked as | ||
retryable via `!PaymentPathFailed::payment_failed_permanently` (#1702). | ||
* Dust HTLCs are now considered failed in the payment tracking logic after the | ||
commitment transaction confirms, allowing retry on restart (#1691). |
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.
Are ChannelMonitors safe to remove now?
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 so now that #1466, #1620, and #1691 are addressed, unless @TheBlueMatt knows of another edge case. In any case, we may want to expose a public helper that users can call instead of relying on the result of get_claimable_balances
.
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.
Yes, I believe so. I don't want to announce it quite yet, though, would rather let the code sit for a release or two and then announce it.
Wondering how people check if any PRs are missing? Maybe we should start tagging all PRs with the release milestone on merge if they aren't tagged already |
Usually with |
My go-to is |
Super handy, thanks! |
CHANGELOG.md
Outdated
to avoid delaying other messages (#1604. #1660, #1683). | ||
* Rather than spawning a full OS thread, `lightning-background-processor` has | ||
a new `process_events_async` method which takes the place of a | ||
`BackgroundProcessor` for those using Rust async (#1657). |
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.
`BackgroundProcessor` for those using Rust async (#1657). | |
`BackgroundProcessor` for those using Rust's `async` (#1657). |
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.
"async" isn't a name? Its a programming paradigm, I don't think it needs `s
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.
Lgtm after outstanding feedback
CHANGELOG.md
Outdated
|
||
## Backwards Compatibility | ||
* The new `current_time` argument to `PeerManager` constructors must be set to | ||
a UNIX timestamp for upgraded nodes. Only new nodes may use a counter (#1699) |
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.
nit: end with period
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 didn't want to put it on a whole new line just for a "." 😭 I dropped the "Only".
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.
List of PRs SGTM
* Dust HTLCs are now considered failed in the payment tracking logic after the | ||
commitment transaction confirms, allowing retry on restart (#1691). | ||
* On machines with buggy "monotonic" clocks, LDK will no longer panic if time | ||
goes backwards (#1692). |
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 don't know if #1659 should be added or to minor.
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.
See #1712 (comment)
7e90cbc
to
e54a795
Compare
Codecov Report
@@ Coverage Diff @@
## main #1712 +/- ##
=======================================
Coverage 90.80% 90.80%
=======================================
Files 86 86
Lines 46482 46482
Branches 46482 46482
=======================================
+ Hits 42208 42210 +2
+ Misses 4274 4272 -2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
e54a795
to
309b239
Compare
309b239
to
c3f5d51
Compare
Now based on #1714 with the CHANGELOG stats fixed and one extra entry for it. |
c3f5d51
to
fb6e869
Compare
Okay, hopefully the last CHANGELOG update, fixed the stats again. |
fb6e869
to
ede5175
Compare
Squashed, the relevant changes are: diff --git a/CHANGELOG.md b/CHANGELOG.md
index 83c13d9d3..df326abab 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -33,2 +33,3 @@
* `Invoice` now derives the std `Hash` trait (#1575).
+ * `{Signed,}RawInvoice::hash` have been renamed `signable_hash` (#1714).
* `chain::AccessError` now derives the std `Debug` trait (#1709).
@@ -78,4 +79,4 @@ in deployments creating outbound 0conf channels.
-In total, this release features 82 files changed, 6227 insertions, 1949
-deletions in 115 commits from 11 authors, in alphabetical order:
+In total, this release features 84 files changed, 6306 insertions, 1960
+deletions in 121 commits from 11 authors, in alphabetical order:
* Arik Sosman |
ede5175
to
ee49030
Compare
1531697
ee49030
to
1531697
Compare
Oops, right, addressed feedback. Note that I switched the date format up cause 9/12 is ambiguous, should probably do that for old dates too but for now I just changed the latest date. |
1531697
to
f5473d5
Compare
$ git diff-tree -U1 ee49030c f5473d50
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 71817b5e9..7736ce67e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,2 +1,2 @@
-# 0.0.111 - 2022-09-09 - "Saturated with Messages"
+# 0.0.111 - Sep 12, 2022 - "Saturated with Messages"
@@ -17,4 +17,4 @@
very difficult to correctly implement (i.e., without blocking). Users
- previously using it should instead pass dependent transactions in via new
- `chain::Confirm::transactions_confirmed` calls (#1663).
+ previously using it should instead pass dependent transactions in via
+ additional `chain::Confirm::transactions_confirmed` calls (#1663).
* `ChannelHandshakeConfig::their_channel_reserve_proportional_millionths` has
@@ -60,5 +60,5 @@
* The new `current_time` argument to `PeerManager` constructors must be set to
- a UNIX timestamp for upgraded nodes, new nodes may use a counter (#1699).
+ a UNIX timestamp for upgraded nodes; new nodes may use a counter (#1699).
* `Balance::CounterpartyRevokedOutputClaimable` will never be generated for
- channels which were observed to go on-chain with LDK versions prior to
+ channels that were observed to go on-chain with LDK versions prior to
0.0.111 (#1495). |
No description provided.