-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Reworking of the jsonrpc server #219
Conversation
2aa2c58
to
5e9a96c
Compare
OK testing it on a server I get the following
looks like the buffer is truncated |
Signed-off-by: Vincenzo Palazzo <[email protected]>
Removed the code that it is not longer used by the previous code refactoring. Signed-off-by: Vincenzo Palazzo <[email protected]>
88d2bed
to
ed6ba58
Compare
Signed-off-by: Vincenzo Palazzo <[email protected]>
Signed-off-by: Vincenzo Palazzo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK ee671ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A single warning that I encountered. Otherwise all the things were good.
continue; | ||
} | ||
|
||
if event.is_invalid() { | ||
log::info!(target: "jsonrpc", "event invalid, unregister event from the tracking one"); | ||
log::warn!(target: "jsonrpc", "event invalid: {:?}", event); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This gives me the warning everytime I run lampo-cli --network regtest getinfo
.
2024-05-24T16:13:35.386Z WARN jsonrpc event invalid: Event { key: Connect, source: Source { fd: 15, events: 519, revents: 32 } }. [lampo-jsonrpc/src/lib.rs:281]
Should we take care of this or should we ignore this everytime.
This is the basic flow of events whenever I am querying the node.
RPCEvent::Accept
RPCEvent::Connect && event.is_readable()
RPCEvent::Connect and the event.is_invalid()
-> This throws the warning.
Alternative version for #216