Skip to content

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

Merged
merged 2 commits into from
Sep 13, 2022
Merged

Cut 0.0.111 #1712

merged 2 commits into from
Sep 13, 2022

Conversation

TheBlueMatt
Copy link
Collaborator

No description provided.

@TheBlueMatt TheBlueMatt added this to the 0.0.111 milestone Sep 9, 2022
* 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).
Copy link
Contributor

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?

Copy link
Contributor

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.

Copy link
Collaborator Author

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.

@valentinewallace
Copy link
Contributor

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

@ariard
Copy link

ariard commented Sep 9, 2022

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 git log from the latest milestone and checking the diff. As iirc we don't care about really minor PRs to be mentioned, so we can't automate things

@wpaulino
Copy link
Contributor

wpaulino commented Sep 9, 2022

Wondering how people check if any PRs are missing?

My go-to is git log --merges v0.0.110..HEAD.

@valentinewallace
Copy link
Contributor

git log --merges v0.0.110..HEAD

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).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`BackgroundProcessor` for those using Rust async (#1657).
`BackgroundProcessor` for those using Rust's `async` (#1657).

Copy link
Collaborator Author

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

Copy link
Contributor

@valentinewallace valentinewallace left a 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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: end with period

Copy link
Collaborator Author

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".

Copy link

@ariard ariard left a 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).
Copy link

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TheBlueMatt TheBlueMatt force-pushed the 2022-09-111 branch 2 times, most recently from 7e90cbc to e54a795 Compare September 9, 2022 20:20
@codecov-commenter
Copy link

codecov-commenter commented Sep 9, 2022

Codecov Report

Merging #1712 (f5473d5) into main (990e346) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           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     
Impacted Files Coverage Δ
lightning/src/ln/monitor_tests.rs 99.44% <0.00%> (-0.12%) ⬇️
lightning/src/ln/functional_tests.rs 96.81% <0.00%> (-0.02%) ⬇️
lightning/src/ln/channelmanager.rs 85.00% <0.00%> (+0.02%) ⬆️
lightning/src/chain/onchaintx.rs 94.71% <0.00%> (+0.68%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@TheBlueMatt
Copy link
Collaborator Author

Rebased on #1710 and filled in all the stats. This should be good to go once #1710 lands (shouldn't have to rebase it either if there's no changes there - the extra merge commit won't change the stats and I calculated them again #1710).

jkczyz
jkczyz previously approved these changes Sep 9, 2022
ariard
ariard previously approved these changes Sep 9, 2022
@TheBlueMatt
Copy link
Collaborator Author

Now based on #1714 with the CHANGELOG stats fixed and one extra entry for it.

@TheBlueMatt
Copy link
Collaborator Author

Okay, hopefully the last CHANGELOG update, fixed the stats again.

@TheBlueMatt
Copy link
Collaborator Author

TheBlueMatt commented Sep 12, 2022

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

jkczyz
jkczyz previously approved these changes Sep 12, 2022
@TheBlueMatt
Copy link
Collaborator Author

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.

@TheBlueMatt
Copy link
Collaborator Author

$ 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).

@TheBlueMatt TheBlueMatt merged commit 4ae65e8 into lightningdevkit:main Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants