Christian Decker b1aed933e6 pyln: Plugin methods and hooks refuse to set results twice ... We had a couple of instances where a plugin would be killed by `lightningd` because we were returning a result of an exception twice, and it was hard to trace down the logic error in the user plugin that caused that. This patch adds a traceback the first time we return a result/exception, and raise an exception with a stacktrace of the first termination when a second one comes in. This can still terminate the plugin, but the programmer gets a clear indication where the result was set, and can potentially even recover from it. Changelog-Added: pyln: Plugin method and hook requests prevent the plugin developer from accidentally setting the result multiple times, and will raise an exception detailing where the result was first set.		2020-10-13 20:52:48 +02:00
..
__init__.py	pyln: Bump versions of pyln-client and pyln-testing	2019-12-31 16:43:04 +01:00
lightning.py	pyln-client: listpayments -> listpays	2020-10-09 13:21:35 +10:30
plugin.py	pyln: Plugin methods and hooks refuse to set results twice	2020-10-13 20:52:48 +02:00