mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-02-21 22:31:48 +01:00
db3707f957
This was pointed out by Daywalker [1]: we are synchronously processing events from `lightningd` which means that if processing one of the hooks or requests was slow or delayed, we would not get notifications, hooks, or RPC requests, massively impacting the flexbility. This highlights the issue with a failing test (it times out), and in the next commit we will isolate event processing into their own task, so to free the event loop from having to wait for an eventual response. [1] https://community.corelightning.org/c/developers/hold-invoice-plugin#comment_wrapper_16754493
23 lines
950 B
Makefile
23 lines
950 B
Makefile
cln-rpc-wrongdir:
|
|
$(MAKE) -C .. cln-rpc-all
|
|
|
|
CLN_RPC_EXAMPLES := target/${RUST_PROFILE}/examples/cln-rpc-getinfo
|
|
CLN_RPC_GENALL = cln-rpc/src/model.rs
|
|
CLN_RPC_SOURCES = $(shell find cln-rpc -name *.rs) ${CLN_RPC_GENALL}
|
|
JSON_SCHEMAS = $(wildcard doc/schemas/*.request.json doc/schemas/*.schema.json)
|
|
DEFAULT_TARGETS += $(CLN_RPC_EXAMPLES) $(CLN_RPC_GENALL)
|
|
|
|
$(CLN_RPC_GENALL): $(JSON_SCHEMAS)
|
|
PYTHONPATH=contrib/msggen python3 contrib/msggen/msggen/__main__.py
|
|
|
|
target/${RUST_PROFILE}/examples/cln-rpc-getinfo: $(shell find cln-rpc -name *.rs)
|
|
cargo build ${CARGO_OPTS} --example cln-rpc-getinfo
|
|
|
|
target/${RUST_PROFILE}/examples/cln-plugin-startup: $(shell find cln-rpc -name *.rs)
|
|
cargo build ${CARGO_OPTS} --example cln-plugin-startup
|
|
|
|
target/${RUST_PROFILE}/examples/cln-plugin-reentrant: $(shell find plugins/examples -name *.rs)
|
|
cargo build ${CARGO_OPTS} --example cln-plugin-reentrant
|
|
|
|
|
|
cln-rpc-all: ${CLN_RPC_GEN_ALL} ${CLN_RPC_EXAMPLES}
|