vincenzopalazzo
/
rgb-cln
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
rgb-cln/lightningd/jsonrpc_errors.h

45 lines
1.4 KiB
C
Raw Normal View History

jsonrpc_errors.h: Header for JSON-RPC errors.
2018-02-05 01:19:16 +00:00
/* lightningd/jsonrpc_errors.h
* Lists error codes for JSON-RPC.
*/
#ifndef LIGHTNING_LIGHTNINGD_JSONRPC_ERRORS_H
#define LIGHTNING_LIGHTNINGD_JSONRPC_ERRORS_H
#include "config.h"
Fix typos
2018-02-08 21:49:35 +00:00
/* Standard errors defined by JSON-RPC 2.0 standard */
jsonrpc_errors.h: Header for JSON-RPC errors.
2018-02-05 01:19:16 +00:00
#define JSONRPC2_INVALID_REQUEST -32600
#define JSONRPC2_METHOD_NOT_FOUND -32601
#define JSONRPC2_INVALID_PARAMS -32602
Added error code parameter to command_fail Until now, `command_fail()` reported an error code of -1 for all uses. This PR adds an `int code` parameter to `command_fail()`, requiring the caller to explicitly include the error code. This is part of #1464. The majority of the calls are used during parameter validation and their error code is now JSONRPC2_INVALID_PARAMS. The rest of the calls report an error code of LIGHTNINGD, which I defined to -1 in `jsonrpc_errors.h`. The intention here is that as we improve our error reporting, all occurenaces of LIGHTNINGD will go away and we can eventually remove it. I also converted calls to `command_fail_detailed()` that took a `NULL` `data` parameter to use the new `command_fail()`. The only difference from an end user perspecive is that bad input errors that used to be -1 will now be -32602 (JSONRPC2_INVALID_PARAMS).
2018-05-24 22:40:18 +01:00
/* Uncategorized error.
* FIXME: This should be replaced in all places
* with a specific error code, and then removed.
*/
#define LIGHTNINGD -1
renamed error code Signed-off-by: Mark Beckwith <wythe@intrig.com>
2018-07-28 18:34:17 +01:00
/* Developer error in the parameters to param() call */
#define PARAM_DEV_ERROR -2
Added error code parameter to command_fail Until now, `command_fail()` reported an error code of -1 for all uses. This PR adds an `int code` parameter to `command_fail()`, requiring the caller to explicitly include the error code. This is part of #1464. The majority of the calls are used during parameter validation and their error code is now JSONRPC2_INVALID_PARAMS. The rest of the calls report an error code of LIGHTNINGD, which I defined to -1 in `jsonrpc_errors.h`. The intention here is that as we improve our error reporting, all occurenaces of LIGHTNINGD will go away and we can eventually remove it. I also converted calls to `command_fail_detailed()` that took a `NULL` `data` parameter to use the new `command_fail()`. The only difference from an end user perspecive is that bad input errors that used to be -1 will now be -32602 (JSONRPC2_INVALID_PARAMS).
2018-05-24 22:40:18 +01:00
pay: Make sendpay nonblocking.
2018-03-04 05:35:37 +00:00
/* Errors from `pay`, `sendpay`, or `waitsendpay` commands */
pay: Provide detailed errors on `sendpay` or `pay` failure. Fixes: #866
2018-02-03 11:46:12 +00:00
#define PAY_IN_PROGRESS 200
#define PAY_RHASH_ALREADY_USED 201
#define PAY_UNPARSEABLE_ONION 202
#define PAY_DESTINATION_PERM_FAIL 203
#define PAY_TRY_OTHER_ROUTE 204
#define PAY_ROUTE_NOT_FOUND 205
#define PAY_ROUTE_TOO_EXPENSIVE 206
payalgo: Create a new failure for paying expired invoice.
2018-02-17 07:34:31 +00:00
#define PAY_INVOICE_EXPIRED 207
pay: Make sendpay nonblocking.
2018-03-04 05:35:37 +00:00
#define PAY_NO_SUCH_PAYMENT 208
#define PAY_UNSPECIFIED_ERROR 209
payalgo: Implement retry_for for pay command.
2018-03-11 14:30:34 +00:00
#define PAY_STOPPED_RETRYING 210
pay: Provide detailed errors on `sendpay` or `pay` failure. Fixes: #866
2018-02-03 11:46:12 +00:00
Added wallet related error codes New codes: FUND_MAX_EXCEEDED, FUND_CANNOT_AFFORD, FUND_DUST_LIMIT_UNMET. The error message "Cannot afford fee" was not exactly correct because it would also occur if the amount requested could not be afforded. So I changed it to the more generic "Cannot afford transaction". Other things: * Fixed off-by-one satoshi in fundchannel manpage. * Changed 'arror' to 'error' because we are not pirates.
2018-06-15 17:45:06 +01:00
/* `fundchannel` or `withdraw` errors */
#define FUND_MAX_EXCEEDED 300
#define FUND_CANNOT_AFFORD 301
wallet: clarify error 302. "Dust limit unmet" seems undescriptive to me. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-06-17 05:48:12 +01:00
#define FUND_OUTPUT_IS_DUST 302
Added wallet related error codes New codes: FUND_MAX_EXCEEDED, FUND_CANNOT_AFFORD, FUND_DUST_LIMIT_UNMET. The error message "Cannot afford fee" was not exactly correct because it would also occur if the amount requested could not be afforded. So I changed it to the more generic "Cannot afford transaction". Other things: * Fixed off-by-one satoshi in fundchannel manpage. * Changed 'arror' to 'error' because we are not pirates.
2018-06-15 17:45:06 +01:00
invoice: Define specific error codes for duplicate label and preimage.
2018-04-26 08:42:04 +01:00
/* Errors from `invoice` command */
#define INVOICE_LABEL_ALREADY_EXISTS 900
#define INVOICE_PREIMAGE_ALREADY_EXISTS 901
Use expected LIGHTNING_DIR_FILE_H define
2018-03-22 10:36:25 +00:00
#endif /* LIGHTNING_LIGHTNINGD_JSONRPC_ERRORS_H */