trueptolemy 96135dab5e log: add 'warning' notification when log ... - Related Changes for `warning` notification Add a `bool` type parameter in `log_()` and `lov()`, this `bool` flag indicates if we should call `warning` notifier. 1) The process of copying `log_book` of every peer to the `log_book` of `ld` is usually included in `log_()` and `lov()`, and it may lead to repeated `warning` notification. So a `bool`, which explicitly indicates if the `warning` notification is disabled during this call, is necessary . 2) The `LOG_INFO` and `LOG_DEBUG` level don't need to call warning, so set that `bool` paramater as `FALSE` for these log level and only set it as `TRUE` for `LOG_UNUAUSL`/`LOG_BROKEN`. As for `LOG_IO`, it use `log_io()` to log, so we needn't think about notifier for it.		2019-06-07 01:23:51 +00:00
..
.gitignore	wallet: move tests into test/ dir like other unit tests.	2017-12-13 22:46:10 +01:00
Makefile	Use node_id everywhere for nodes.	2019-04-09 12:37:16 -07:00
run-db.c	log: add 'warning' notification when log	2019-06-07 01:23:51 +00:00
run-wallet.c	log: add 'warning' notification when log	2019-06-07 01:23:51 +00:00
test_utils.c	chore: increase min-capacity-sat to 10k	2019-04-16 15:01:28 -07:00
test_utils.h	fix: a pr2444 introduced valgrind complaint	2019-03-14 16:51:18 +01:00