Skip to content

Harden test for logging of inbound htlc being resolved #281

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

Conversation

ariard
Copy link

@ariard ariard commented Dec 30, 2018

A nit, but occured to me while reviewing 278 than we could harden test there (timeout tx resolving inbound htlc output nothing to broadcast/pass upstream, just logging)

@TheBlueMatt
Copy link
Collaborator

Isn't this guaranteed? Can we just debug_assert!() it?

@ariard ariard force-pushed the harden-inbound-htlc-resolved branch from adec08a to cb53ae7 Compare January 3, 2019 02:07
@ariard
Copy link
Author

ariard commented Jan 3, 2019

Oh in fact no, we forgot to log apart offered HTLC being resolved by HTLC-timeout, have a look on test_justice_tx (HTLC-timeout on revoked remote commitment tx) or test_htlc_ignore_latest_remote_commitment_tx (HTLC-timeout on remote commitment tx)

@TheBlueMatt
Copy link
Collaborator

TheBlueMatt commented Jan 5, 2019 via email

@TheBlueMatt TheBlueMatt merged commit 0faf7bb into lightningdevkit:master Jan 5, 2019
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.

2 participants