bug: Resource temporarily unavailable

[Harshit933]

This is the stack trace. When I tried to to ran lampo-cli getinfo.

2024-01-29T11:06:27.793Z INFO lampo_channel_manager listening on chain event on the channel manager. [lampod/src/ln/channe_manager.rs:145]
2024-01-29T11:06:27.796Z INFO lampo Litening for in-bound connection on 0.0.0.0:19735. [lampod/src/ln/peer_manager.rs:147]
2024-01-29T11:07:10.151Z INFO jsonrpc blocking with err Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }!. [lampo-jsonrpc/src/lib.rs:225]
2024-01-29T11:07:10.151Z INFO jsonrpc buffer read {"method":"getinfo","params":{},"id":"0". [lampo-jsonrpc/src/lib.rs:232]

Although lampo does not crashes but it is not usable. Is this related to #120?

[vincenzopalazzo]

This is the stack trace.

It is not a stacktrace, is a log line at the info level

but it is not usable.

define not usable, WouldBlock is an expected error while you are trying to write async code

To me this is good, what is the behaviours that you are experiencing?

[Harshit933]

I did not get any output after running lampo-cli getinfo. This is what I got.

harshit@harshit:~$ lampo-cli getinfo
✗ JSON decode error: Connection reset by peer (os error 104)

[vincenzopalazzo]

Closing in favor of #184

[vincenzopalazzo]

I reproduced by changing cloud machine

➜  ~ lampo-cli --network testnet fundchannel --node_id 030b686a163aa2bba03cebb8bab7778fac251536498141df0a436d688352d426f6 --amount 4000000000 --public true --node_id 030b686a163aa2bba03cebb8bab7778fac251536498141df0a436d688352d426f6 --addr 65.108.246.14 --port 19735
✗ Error: JSON decode error: Connection reset by peer (os error 104)
➜  ~ lampo-cli --network testnet getinfo
✗ Error: IO error response: No such file or directory (os error 2)

I think the bug is inside the lampo-jsonrpc

[Harshit933]

I think this could be related to the unixlistener. This is the documentation surrounding the set_nonblocking() method inside unixlistener.

/// This will result in the `accept` operation becoming nonblocking,
/// i.e., immediately returning from their calls. If the IO operation is
/// successful, `Ok` is returned and no further action is required. If the
/// IO operation could not be completed and needs to be retried, an error
/// with kind [`io::ErrorKind::WouldBlock`] is returned.

[vincenzopalazzo]

I think the problem is inside my jsonrpc implementation