Carsten Otto

To reproduce: ``` [Tor] tor.active=1 tor.skip-proxy-for-clearnet-targets=true tor.v3=1 ``` `lncli connect 027ce055380348d7812d2ae7745701c9f93e70c1adeb2657f053f91df4f2843c71@[2a01:4f8:c2c:e8a0::1]:9735` Please remove the "missing reproduction" tag.

Note that this breaks/changes `lncli openchannel` and possibly other commands as indicated in https://cli.urfave.org/migrate-v1-to-v2/. As an examply, previously this worked: `lncli openchannel 03...pubkey --local_amt 1000000 --sat_per_vbyte 1` Because `node_key` and...

I just realized that in the following command invocation the "--sat_per_vbyte" flag is silently ignored, which is extremely bad. Just based on this, I'd recommend NOT merging this. I'll leave...

I'm said peer. Let me know if you need further information.

I can't find a single entry in the recent logs (~1 month).

I guess you mean 99828b8ebb72e18be69a7870d5342d20a748412c? That's included in 115b0418747ba941875bd9f2be1bb18754f6f636.

> I can't find a single entry in the recent logs (~1 month). I just realized that I've only started using the new code yesterday, which also means that older...

> Did you started using the new code yesterday AFTER the force close? If so this solves the case. Next warning message should not trigger any force close/channel failure. That...

Yeah, that'd make sense. As a node operator I mainly care about the issues I see, though, and I don't think I've ever seen a "htlc too large". That might...

I'd still like to see the log message, just limited to the case that the amount isn't available in any channel to the peer.