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

[Feature Request]: Get rid of the node database full warning message. #5282

Closed
JurajKubrican opened this issue Nov 8, 2024 · 0 comments · Fixed by #5292
Closed

[Feature Request]: Get rid of the node database full warning message. #5282

JurajKubrican opened this issue Nov 8, 2024 · 0 comments · Fixed by #5292
Labels
enhancement New feature or request

Comments

@JurajKubrican
Copy link

JurajKubrican commented Nov 8, 2024

Platform

Cross-Platform

Description

Maybe it's just my local group, but people keep being paranoid about their node DB being full, I keep telling them that it's not an issue ant the db auto-rotates and it shouldn't cause any issues but this concern keeps popping up.

this is the scenario:

  • My node is low/unstable/disconnects .. whatever
  • I take a look at the device screen
  • says warning node b full!
  • I spend hours curating by node db instead of updating/reporting an unstability, deleting longFast channel in order not to have "too many nodes"

I feel like this warning message doesn't actually bring value as there is nothing one can reasonably do about it, and can mislead people into thinking deleting nodes will actually solve some issues they might be having

@JurajKubrican JurajKubrican added the enhancement New feature or request label Nov 8, 2024
@JurajKubrican JurajKubrican changed the title [Feature Request]: Get rid of the node database full arning message. [Feature Request]: Get rid of the node database full warning message. Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant