aljaz/lightning
1
0
Fork 0
mirror of https://github.com/aljazceru/lightning.git synced 2025-12-19 15:14:23 +01:00
Code Issues Packages Projects Releases Wiki Activity

pyln: Fix backward compat issue in LightningRpc.close

Browse Source 
The issue is that the new keyword `force_lease_closed` was being set
even if the user didn't specify it, which results in breakage if this
new pyln version talks to older c-lightning nodes that don't have this
keyword yet. By setting the default to `None` it gets filtered out if
the user has not explicitly set it, but still retains the `True` /
`False` values if they did.

Changelog-None Issue is not present in released versions
This commit is contained in:
Christian Decker
2021-07-27 12:10:31 +02:00
committed by Rusty Russell
parent 7bde0ead4d
commit d732fa9724
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
contrib/pyln-client/pyln/client/lightning.py
View File

@@ -515,7 +515,8 @@ class LightningRpc(UnixDomainSocketRpc):
payload.update({k: v for k, v in kwargs.items()}) payload.update({k: v for k, v in kwargs.items()})
return self.call("check", payload) return self.call("check", payload)
def close(self, peer_id, unilateraltimeout=None, destination=None, fee_negotiation_step=None, force_lease_closed=False): def close(self, peer_id, unilateraltimeout=None, destination=None,
fee_negotiation_step=None, force_lease_closed=None):
""" """
Close the channel with peer {id}, forcing a unilateral Close the channel with peer {id}, forcing a unilateral
close after {unilateraltimeout} seconds if non-zero, and close after {unilateraltimeout} seconds if non-zero, and