-
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
Add a test for 'fundchannel_start' crash on deconnection #6
Add a test for 'fundchannel_start' crash on deconnection #6
Commits on Aug 9, 2019
-
Added possibility to configure max_concurrent_htlcs value for our cha…
…nnels. Eclaire has a default of 30 and I thought why not going with their value and while doing so make it configureable.
Configuration menu - View commit details
-
Copy full SHA for 8e7428d - Browse repository at this point
Copy the full SHA 8e7428dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1dd8908 - Browse repository at this point
Copy the full SHA 1dd8908View commit details -
included feedback by Rusty to check the max_concurrent_htlc value for…
… both peers of a channel
Configuration menu - View commit details
-
Copy full SHA for dfac1d1 - Browse repository at this point
Copy the full SHA dfac1d1View commit details -
pytest: enable deprecated APIs for multi-arg closes.
We're about to change the API, so this makes the tests still work across the transition (and, as a bonus, tests our backwards compat shim). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for b35dc46 - Browse repository at this point
Copy the full SHA b35dc46View commit details -
close: change to a unilateraltimeout argument.
`close` takes two optional arguments: `force` and `timeout`. `timeout` doesn't timeout the close (there's no way to do that), just the JSON call. `force` (default `false`) if set, means we unilaterally close at the timeout, instead of just failing. Timing out JSON calls is generally deprecated: that's the job of the client. And the semantics of this are confusing, even to me! A better API is a timeout which, if non-zero, is the time at which we give up and unilaterally close. The transition code is awkward, but we'll manage for the three releases until we can remove it. The new defaults are to unilaterally close after 48 hours. Fixes: ElementsProject#2791 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 83e654a - Browse repository at this point
Copy the full SHA 83e654aView commit details -
pytest: don't use deprecated options for close() in tests.
Only downside is you have to wait 1 second at least before unilaterally closing. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 0edc0ae - Browse repository at this point
Copy the full SHA 0edc0aeView commit details -
gossipd: check that we don't try to access a deleted gossip entry.
We ignored this before, which meant that the DEVELOPER-mode check that we delete the correct record didn't check that it wasn't already deleted. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for f9ecc76 - Browse repository at this point
Copy the full SHA f9ecc76View commit details -
lightningd: fix crash when peer disconnects after fundchannel_start, …
…before cancel/complete Fixes: ElementsProject#2831 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 710d015 - Browse repository at this point
Copy the full SHA 710d015View commit details -
Configuration menu - View commit details
-
Copy full SHA for cd32da6 - Browse repository at this point
Copy the full SHA cd32da6View commit details