Suggest increasing busy_timeout to prevent errors

[KnockOnWoodNode]

Change Description

Update of SQLite doc to explain how busy_timeout can be tweaked to reduce SQLITE_BUSY errors.

Steps to Test

Nothing special, this follows up with #7869

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

• The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
• Commits follow the Ideal Git Commit Structure.
• Any new logging statements use an appropriate subsystem and logging level.
• There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our Contribution Guidelines for further guidance.

[yyforyongyu]

Thanks for the PR! However I don't think we need it after #7927. For future PRs, please read the contribution guidelines regarding how to write commit messages.

[yyforyongyu]

This line should be wrapped. Also I think this is no longer true after #7927

[KnockOnWoodNode]

So what is missing, is that I didn't provide an extended description for the edit other than the commit title, and I didn't wrap the text in the md?
On a side note, why does a simple md edit fail some of the tests?

From my understanding, the new PR you cited will only prevent SQLite timeouts from causing issues, rather than prevent them entirely, am I wrong? I'd rather prefer my db backend doesn't hit timeout errors at all.

[yyforyongyu]

So what is missing, is that I didn't provide an extended description for the edit other than the commit title, and I didn't wrap the text in the md?

You need to add a prefix as instructed here,

the commit header message should begin with the prefix of the modified package. For example, if a commit was made to modify the lnwallet package, it should start with lnwallet: .

So just simply put a prefix docs: suggest...

On a side note, why does a simple md edit fail some of the tests?

We have test flakes and we are in the process of fixing them.

From my understanding, the new PR you cited will only prevent SQLite timeouts from causing issues, rather than prevent them entirely, am I wrong? I'd rather prefer my db backend doesn't hit timeout errors at all.

It will catch the SQLITE_BUSY error and retry the transaction up to 10 times. Maybe we could document this behavior as well?

That being said, still feels weird to see the SQLITE_BUSY error as lnd only has one database connection.

[KnockOnWoodNode]

Closing and starting a new PR that follows the suggestions above