core-lightning/tests/plugins/fail_htlcs.py

#!/usr/bin/env python3

from lightning import Plugin

plugin = Plugin()


@plugin.hook("htlc_accepted")
def on_htlc_accepted(onion, plugin, **kwargs):
    plugin.log("Failing htlc on purpose")
    plugin.log("onion: %r" % (onion))
    return {"result": "fail", "failure_code": 16399}


plugin.run()
pytest: Add tests for htlc_accepted_hook Two tests: one for failures and one for in-path resolution. Signed-off-by: Christian Decker <decker.christian@gmail.com> 2019-01-11 22:39:18 +01:00			`#!/usr/bin/env python3`

			`from lightning import Plugin`

			`plugin = Plugin()`


			`@plugin.hook("htlc_accepted")`
pylightning: Warn users of plugins that may break due to extra args We recently noticed that the way we unpack the call arguments for hooks and notifications in pylightning breaks pretty quickly once you start changing the hook and notification params. If you add params they will not get mapped correctly causing the plugin to error out. This can be fixed by adding a `VAR_KEYWORD` argument to the calbacks, i.e., by adding a single `**kwargs` argument at the end of the signature. This commit adds a check that such a catch-all argument exists, and emits a warning if it doesn't. It also fixes up the plugins that we ship ourselves. Signed-off-by: Christian Decker <decker.christian@gmail.com> 2019-08-05 02:19:48 +02:00			`def on_htlc_accepted(onion, plugin, **kwargs):`
pytest: Add tests for htlc_accepted_hook Two tests: one for failures and one for in-path resolution. Signed-off-by: Christian Decker <decker.christian@gmail.com> 2019-01-11 22:39:18 +01:00			`plugin.log("Failing htlc on purpose")`
			`plugin.log("onion: %r" % (onion))`
			`return {"result": "fail", "failure_code": 16399}`


			`plugin.run()`