-
Notifications
You must be signed in to change notification settings - Fork 1
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
Miscellaneous patches #6
Conversation
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.
just a couple of nits, otherwise LGTM
lightning/src/util/events.rs
Outdated
@@ -462,7 +462,9 @@ pub enum BumpTransactionEvent { | |||
/// [`BaseSign::sign_holder_htlc_transaction`]: crate::chain::keysinterface::BaseSign::sign_holder_htlc_transaction | |||
/// [`HTLCDescriptor::tx_input_witness`]: HTLCDescriptor::tx_input_witness | |||
HTLCResolution { | |||
/// |
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 those empty comments necessary?
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.
Fixed!
In order to avoid an `unwrap` when building `ChannelDetails`.
Not super important because we are not currently relying on these tests, but it's always easier to develop if all the code builds.
The amount for HTLC #6 was updated in the spec's test vectors, but the "same amount and preimage" test vector itself was not updated, even though the new HTLC amount resulted in a different commitment transaction, and thus, different signatures.
The motivation for 38c54c5, ab73cce and 40bd0c4 is to be able to use the async background processor without problems. These bug fixes are part of 0.0.115.
40bd0c4 is useful because the disconnects are important for debugging at the moment, but TRACE-level logs are too noisy in that module.
d6e4ba8 is not so important so we could drop it, but it's also very simple so it can't hurt.
b4e4eb0 might be the most controversial, but we did run into a related
unwrap
a few times, so it seemed like a good idea at the time.