core-lightning/tests/plugins/fail_htlcs.py

#!/usr/bin/env python3

from pyln.client 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))
    # WIRE_TEMPORARY_NODE_FAILURE = 0x2002
    return {"result": "fail", "failure_message": "2002"}


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`

pyln: Migrate remaining uses of the deprecated pylightning module `pylightning` is not much more than an alias for `pyln-client`, so this removes the need to install that as well just to run the tests. 2020-02-11 23:04:21 +01:00			`from pyln.client import Plugin`
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 = 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))`
plugins: support failure_message in invoice and htlc_accepted hooks. As promised in the Changelog when we converted from failcodes to messages internally. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-02-21 06:10:45 +01:00			`# WIRE_TEMPORARY_NODE_FAILURE = 0x2002`
			`return {"result": "fail", "failure_message": "2002"}`
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.run()`