You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
faelenor opened this issue
Sep 8, 2024
· 1 comment
Labels
bugSomething isn't workingstaleIssue that appear to be inactive, mark for potenial closing if stale for longer timetriageThis is a new issue to be sorted (automatic label)
When there's no sonar.conf file, the sonar service restarts every 5-10 seconds, creating huge CPU spikes (100% for a fraction of a second). I reported the issue to the Mainsail team, but I thought that it was important to report it here as well because installing Klippain will trigger this unless you had previously uninstalled Sonar.
Additional information and klippy.log
No response
The text was updated successfully, but these errors were encountered:
📌 This issue has been marked as stale because it has not had activity in the past 30 days.
To keep it open, please respond to this message or add new information. Otherwise, this will be closed in 14 days.
Thank you for your contributions!
github-actionsbot
added
the
stale
Issue that appear to be inactive, mark for potenial closing if stale for longer time
label
Oct 9, 2024
bugSomething isn't workingstaleIssue that appear to be inactive, mark for potenial closing if stale for longer timetriageThis is a new issue to be sorted (automatic label)
Klippain branch
Version
v4.3.1-17-gdf5ad5bf
Describe the bug and expected behavior
When there's no sonar.conf file, the sonar service restarts every 5-10 seconds, creating huge CPU spikes (100% for a fraction of a second). I reported the issue to the Mainsail team, but I thought that it was important to report it here as well because installing Klippain will trigger this unless you had previously uninstalled Sonar.
Additional information and klippy.log
No response
The text was updated successfully, but these errors were encountered: