neil saitug

Deferring to next release pending small fixes.

> Seems there is one json scan that doesn't always match the payload: > > ``` > `openchannel2` payload did not scan Parsing '{openchannel2:{id:%,channel_id:%,their_funding_msat:%,max_htlc_value_in_flight_msat:%,htlc_minimum_msat:%,funding_feerate_per_kw:%,commitment_feerate_per_kw:%,feerate_our_max:%,feerate_our_min:%,to_self_delay:%,max_accepted_htlcs:%,channel_flags:%,locktime:%,channel_max_msat:': object does not have member channel_max_msat:...

Ok so it sounds like one of your plugins is failing to start, and taking the node down with it. We changed the msats APIs recently, which caused problems for...

lil note that @nassersaazi is tentatively going to take a crack at this

Whoa this is a great idea. I think the easiest thing to do would be more "blackbox", so having a shell function that calls `mkfunding` with some parameters and verifies...

Note that there's a partial fix for `mkfunding` here (still has crash) https://github.com/ElementsProject/lightning/commit/d2ea7f25fa1a5271096067fd4b666064d4054948

maybe #5601

Does the node appear to be connected when it has this issue? I think you can check this in `listpeers`, it'll say `connected: true/false`.

does #5585 or #5584 fix this?

caused by a poetry install failure, think we've fixed this now?