• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

lightningnetwork / lnd / 12343072627

15 Dec 2024 11:09PM UTC coverage: 57.504% (-1.1%) from 58.636%
12343072627

Pull #9315

github

yyforyongyu
contractcourt: offer outgoing htlc one block earlier before its expiry

We need to offer the outgoing htlc one block earlier to make sure when
the expiry height hits, the sweeper will not miss sweeping it in the
same block. This also means the outgoing contest resolver now only does
one thing - watch for preimage spend till height expiry-1, which can
easily be moved into the timeout resolver instead in the future.
Pull Request #9315: Implement `blockbeat`

1445 of 2007 new or added lines in 26 files covered. (72.0%)

19246 existing lines in 249 files now uncovered.

102342 of 177975 relevant lines covered (57.5%)

24772.24 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

58.33
/htlcswitch/failure_detail.go
1
package htlcswitch
2

3
// FailureDetail is an interface implemented by failures that occur on
4
// our incoming or outgoing link, or within the switch itself.
5
type FailureDetail interface {
6
        // FailureString returns the string representation of a failure
7
        // detail.
8
        FailureString() string
9
}
10

11
// OutgoingFailure is an enum which is used to enrich failures which occur in
12
// the switch or on our outgoing link with additional metadata.
13
type OutgoingFailure int
14

15
const (
16
        // OutgoingFailureNone is returned when the wire message contains
17
        // sufficient information.
18
        OutgoingFailureNone OutgoingFailure = iota
19

20
        // OutgoingFailureDecodeError indicates that we could not decode the
21
        // failure reason provided for a failed payment.
22
        OutgoingFailureDecodeError
23

24
        // OutgoingFailureLinkNotEligible indicates that a routing attempt was
25
        // made over a link that is not eligible for routing.
26
        OutgoingFailureLinkNotEligible
27

28
        // OutgoingFailureOnChainTimeout indicates that a payment had to be
29
        // timed out on chain before it got past the first hop by us or the
30
        // remote party.
31
        OutgoingFailureOnChainTimeout
32

33
        // OutgoingFailureHTLCExceedsMax is returned when a htlc exceeds our
34
        // policy's maximum htlc amount.
35
        OutgoingFailureHTLCExceedsMax
36

37
        // OutgoingFailureInsufficientBalance is returned when we cannot route a
38
        // htlc due to insufficient outgoing capacity.
39
        OutgoingFailureInsufficientBalance
40

41
        // OutgoingFailureCircularRoute is returned when an attempt is made
42
        // to forward a htlc through our node which arrives and leaves on the
43
        // same channel.
44
        OutgoingFailureCircularRoute
45

46
        // OutgoingFailureIncompleteForward is returned when we cancel an incomplete
47
        // forward.
48
        OutgoingFailureIncompleteForward
49

50
        // OutgoingFailureDownstreamHtlcAdd is returned when we fail to add a
51
        // downstream htlc to our outgoing link.
52
        OutgoingFailureDownstreamHtlcAdd
53

54
        // OutgoingFailureForwardsDisabled is returned when the switch is
55
        // configured to disallow forwards.
56
        OutgoingFailureForwardsDisabled
57
)
58

59
// FailureString returns the string representation of a failure detail.
60
//
61
// Note: it is part of the FailureDetail interface.
62
func (fd OutgoingFailure) FailureString() string {
9✔
63
        switch fd {
9✔
64
        case OutgoingFailureNone:
×
65
                return "no failure detail"
×
66

67
        case OutgoingFailureDecodeError:
×
68
                return "could not decode wire failure"
×
69

70
        case OutgoingFailureLinkNotEligible:
1✔
71
                return "link not eligible"
1✔
72

UNCOV
73
        case OutgoingFailureOnChainTimeout:
×
UNCOV
74
                return "payment was resolved on-chain, then canceled back"
×
75

76
        case OutgoingFailureHTLCExceedsMax:
2✔
77
                return "htlc exceeds maximum policy amount"
2✔
78

79
        case OutgoingFailureInsufficientBalance:
1✔
80
                return "insufficient bandwidth to route htlc"
1✔
81

82
        case OutgoingFailureCircularRoute:
1✔
83
                return "same incoming and outgoing channel"
1✔
84

85
        case OutgoingFailureIncompleteForward:
3✔
86
                return "failed after detecting incomplete forward"
3✔
87

88
        case OutgoingFailureDownstreamHtlcAdd:
×
89
                return "could not add downstream htlc"
×
90

91
        case OutgoingFailureForwardsDisabled:
1✔
92
                return "node configured to disallow forwards"
1✔
93

94
        default:
×
95
                return "unknown failure detail"
×
96
        }
97
}
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc