wallet: improve logging around transaction broadcast failures#7513
Merged
guggero merged 1 commit intolightningnetwork:masterfrom Apr 11, 2023
Merged
wallet: improve logging around transaction broadcast failures#7513guggero merged 1 commit intolightningnetwork:masterfrom
guggero merged 1 commit intolightningnetwork:masterfrom
Conversation
guggero
force-pushed
the
publish-tx-logging
branch
from
678b871 to
9ee7e44
Compare
Collaborator
Author
|
Rebased and updated after depending PR was merged. |
Collaborator
|
@Roasbeef: review reminder |
Member
|
Needs a rebase then this can land. |
guggero
force-pushed
the
publish-tx-logging
branch
from
9ee7e44 to
154e654
Compare
Collaborator
Author
|
The |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #7505.
Depends on btcsuite/btcwallet#851.The logging around transaction broadcast failures has been improved by always logging the causing error and the raw transaction as hex.