nicolasburtey

do you know if there is a way to mitigate such issues? Worth opening a ticket on the main lnd repo? The issue happened probably 2 lnd version ago. I...

``` "resolutions": [ { "resolution_type": "OUTGOING_HTLC", "outcome": "TIMEOUT", "outpoint": { "txid_bytes": "471095411fe2f602526c92f79d74420ce2c5861833f929fbb2855d75f3185fd8", "txid_str": "d85f18f3755d85b2fb29f9331886c5e20c42749df7926c5202f6e21f41951047", "output_index": 0 }, "amount_sat": "373777", "sweep_txid": "fcfd551b8dad977156399bb368f34bbb8ced5fbfb3c19f9360e5a90428bb01f2" }, { "resolution_type": "OUTGOING_HTLC", "outcome": "TIMEOUT", "outpoint": { "txid_bytes":...

this is a good start. some comment: - I feel where typing might be most useful for return so that errors can be managed properly. inputs are useful for auto-completion...

beyond adding type in a separate .d.ts file (much like a .h for a .c), a relevant solution could be to have the library being developed in typescript and compile...

off-topic, but what is the goal of https://github.com/alexbosworth/lightning compared to ln-service?

that works. thanks!

I'm actually running into the same issue with subscribeToChannels.

this would be awesome :)

Jest is giving me this weird error: ``` 1 CANCELLED: Cancelled at Object.exports.createStatusError (node_modules/grpc/src/common.js:91:15) at ClientReadableStream._emitStatusIfDone (node_modules/grpc/src/client.js:233:26) at ClientReadableStream._readsDone (node_modules/grpc/src/client.js:199:8) at node_modules/grpc/src/client_interceptors.js:683:15 ``` Trying to investigate where that could come...

if I comment a line with `once(sub, 'channel_opened')`, then the error disappeared. But for some reason, the error was not here with the last tagged version. weird. any clue about...