chanfunding: improve sanityCheckFee error message for clarity

[myxmaster]

I was confused about this error msg, so I suggest this rewording.

[guggero]

Argh, it looks like some unit tests match on the error message:

 --- FAIL: TestCoinSelectUpToAmount (0.00s)
    --- FAIL: TestCoinSelectUpToAmount/high_fee (0.00s)
        coin_select_test.go:887: 
            	Error Trace:	/home/runner/work/lnd/lnd/lnwallet/chanfunding/coin_select_test.go:887
            	Error:      	Error message not equal:
            	            	expected: "fee 0.00000192 BTC on total output value 0.00000768 BTC"
            	            	actual  : "fee (0.00000192 BTC) exceeds 20% of total output (0.00000768 BTC)"
            	Test:       	TestCoinSelectUpToAmount/high_fee

Perhaps we should instead focus on #8600, which also makes this fraction configurable?

[myxmaster]

Haha ok, I was briefly looking at the test, but didn't see that.

Well, you are right with focusing on #8600. Since I have no idea how long that takes, let me know if a quick/dirty fix for the test is wanted.

[guggero]

Yeah, a quick fix to

lnd/lnwallet/chanfunding/coin_select_test.go

Line 414 in e99e666

expectErr: "fee 0.00000045 BTC on total output value " +

would be appreciated (maybe other places too, you can verify by running make unit pkg=lnwallet/chanfunding to test, since that was the only package that failed).

[coderabbitai]

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)

• llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[myxmaster]

Alright, should be good to go now.

(sry for so many commits, doing this on github webinterface 😂 and it cant amend commits in here...)

[guggero]

Approved CI run. But we usually don't merge with squash. So would be great if you could squash the commits into one using the command line (or something else than the UI).

[guggero]

Linter failing. You can check locally with make lint to avoid needing to wait for anyone of us to approve each CI run.

[myxmaster]

Alright, now I understand the indentation logic, I misunderstood the "8 char" info I read somewhere...

Linter passes now.