mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-01-18 05:12:45 +01:00
871d0b1d74
We have to do a dance when we get a reconnect in openingd, because we don't normally expect to free both owner and peer. It's a layering violation: freeing a peer should clean up the owner's pointer to it, to avoid a double free, and we can eliminate this dance. The free order is now different, and the test_reconnect_openingd was overprecise. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
---|---|---|
.. | ||
requirements.txt | ||
test_lightningd.py | ||
utils.py |