Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cfg: fail startup on flags.Error parsing error #8822

Merged

Conversation

michael1011
Copy link
Contributor

@michael1011 michael1011 commented Jun 10, 2024

Change Description

Fixes the issue of @theborakompanioni when updating to LND v0.18.0-beta: #7867 (comment)

Having removed option groups in the config caused the config file parser to throw an error, but that error is flags.Error which only printed a warning but did not prevent starting the node.

Steps to Test

Steps for reviewers to follow to test the change.

Pull Request Checklist

Testing

  • Your PR passes all CI checks.
  • Tests covering the positive and negative (error paths) are included.
  • Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

📝 Please see our Contribution Guidelines for further guidance.

Copy link
Contributor

coderabbitai bot commented Jun 10, 2024

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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@guggero guggero mentioned this pull request Jun 10, 2024
@theborakompanioni
Copy link
Contributor

Wow, amazingly fast @michael1011 🚀
Thank you. 🙏

With this change applied, the daemon prints the error message and refuses to proceed the booting sequence, right?

@michael1011
Copy link
Contributor Author

Wow, amazingly fast @michael1011 🚀 Thank you. 🙏

With this change applied, the daemon prints the error message and refuses to proceed the booting sequence, right?

Exactly

./lnd-debug 
failed to load config: could not find option group `Litecoin'

Copy link
Collaborator

@guggero guggero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch, thanks for the fix!

config.go Outdated Show resolved Hide resolved
@michael1011 michael1011 force-pushed the fix-config-error-handling branch 2 times, most recently from d037dfb to 1f45e10 Compare June 10, 2024 13:24
config.go Outdated
@@ -771,7 +772,7 @@ func LoadConfig(interceptor signal.Interceptor) (*Config, error) {
// If it's a parsing related error, then we'll return
// immediately, otherwise we can proceed as possibly the config
// file doesn't exist which is OK.
if _, ok := err.(*flags.IniError); ok {
if lnutils.ErrorAs[*flags.IniError](err) || lnutils.ErrorAs[*flags.Error](err) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess one thing that needs to be tested is if the comment above still stands true? Meaning, do we still ignore a non-existing file? Or is that returned as a *flags.Error?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The file not existing returns a *fs.PathError

@michael1011
Copy link
Contributor Author

Now the linter should be happy

Copy link
Collaborator

@guggero guggero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK, LGTM 🎉

@saubyk saubyk added this to the v0.18.1 milestone Jun 10, 2024
Copy link
Collaborator

@ziggie1984 ziggie1984 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the Fix, LGTM 🤝

EDIT: Missing Release-Notes for LND 18.1

Copy link
Contributor

@theborakompanioni theborakompanioni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK 🚀

Copy link
Collaborator

@guggero guggero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One last nit, otherwise LGTM 🎉

docs/release-notes/release-notes-0.18.1.md Outdated Show resolved Hide resolved
@michael1011 michael1011 force-pushed the fix-config-error-handling branch 2 times, most recently from b9d37e2 to 373a573 Compare June 10, 2024 19:20
@ellemouton
Copy link
Collaborator

@michael1011 - can you rebase onto latest master pls? 🙏

@michael1011
Copy link
Contributor Author

Rebased @ellemouton

@Roasbeef Roasbeef merged commit c0f7c28 into lightningnetwork:master Jun 19, 2024
27 of 32 checks passed
@michael1011 michael1011 deleted the fix-config-error-handling branch June 19, 2024 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants