-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
offer: fix typo to the getchaininfo rpc #7321
offer: fix typo to the getchaininfo rpc #7321
Conversation
39fa1c0
to
acb054f
Compare
wondering if this was already fixed in some commit
I should look more at the git history |
The port reserve issue was just introduced by two PRs merged in quick succession. I think this commit should resolve it if you want to cherry-pick it. |
Ah ok I remember that I see something that was fixing this problem :) Well I ack the PR and then I will rebase on top of yours, thanks |
acb054f
to
ce8baa9
Compare
Trivial rebased on master, now this should include the @endothermicdev patch, thanks! |
ce8baa9
to
476cdfb
Compare
Please note that 476cdfb It is my fault that I made this a requirement parameter, this should be optional to allow use cases like the offer plugin. |
476cdfb
to
ef8686d
Compare
I think the commits are out of order here - the argument should be made optional before it stops being passed. LGTM otherwise. |
ef8686d
to
8372ed6
Compare
This is on me, and the last height is optional, and not required, because sometimes you do not want wait the sync of the blockchain but just get the information of the current status. Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is violate what the docs of getchainfo is telling us that the last_block_height is a u64. ``` 2024-05-17T09:53:23.464Z **BROKEN** plugin-offers: Got error reply to getchaininfo: '{\"error\":{\"code\":-1,\"data\":null,\"message\":\"invalid type: string \\\"0\\\", expected u64\"},\"id\":\"init/offers:getchaininfo#1\",\"jsonrpc\":\"2.0\"}\n\n' 2024-05-17T09:53:23.496Z INFO plugin-offers: Killing plugin: exited before replying to init 2024-05-17T09:53:23.496Z **BROKEN** plugin-offers: Plugin marked as important, shutting down lightningd! 2024-05-17T09:53:23.496Z DEBUG lightningd: io_break: lightningd_exit 2024-05-17T09:53:23.496Z **BROKEN** plugin-topology: Reading JSON input: Connection reset by peer 2024-05-17T09:53:23.504Z INFO plugin-topology: Killing plugin: exited before replying to init 2024-05-17T09:53:23.504Z **BROKEN** plugin-topology: Plugin marked as important, shutting down lightningd! 2024-05-17T09:53:23.504Z DEBUG lightningd: io_break: lightningd_exit 2024-05-17T09:53:23.504Z DEBUG plugin-bookkeeper: Setting up database at sqlite3://accounts.sqlite3 2024-05-17T09:53:23.504Z DEBUG connectd: REPLY WIRE_CONNECTD_START_SHUTDOWN_REPLY with 0 fds 2024-05-17T09:53:23.504Z DEBUG lightningd: io_break: connectd_start_shutdown_reply ``` Fixing the following crash ``` Got error reply to getchaininfo: '{"error":{"code":-1,"data":null,"message":"invalid type: string \"0\", expected u64"},"id":"init/offers:getchaininfo#1","jsonrpc":"2.0"} 'lightningd: lightningd already running? Error locking PID file: Resource temporarily unavailable ``` Fixes: 847208f Changelog-None: offer: fix type to the getchaininfo rpc Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
8372ed6
to
6cb4a72
Compare
Rebased and addressing the review, thanks @endothermicdev |
This is violate what the docs of getchainfo are telling us that the last_block_height is a u64.
Fixing the following crash
Changelog-None: offer: fix type to the getchaininfo rpc