Feature summary
An error loop may create a log every ms, ending up filling a disk
What problem are you trying to solve?
This is especially true on chromebook, it is quite random, but sometime when I come back and unlock my session, the process start logging "Audio output stream failed: a backend-specific error has occurred: alsa::poll() returned POLLERR" indefinitly (well unmutting the host sound make this disapears) but anyway the log size increase by 5Gb every minutes meaning the disk is full in a jiffy.
The log file with this issue is "github-app.{pid}.log".
Proposed solution
Would it be possible to limit the size of this file to let say 1Gb and make it rolling (keep 5 file maximum) + an alert "warning rolling log file, check why you have so many logs" .
Workflow impact
no need to clean file to continue working, warning on strange alert if there are.
Installation context
No response
Additional context
No response
Feature summary
An error loop may create a log every ms, ending up filling a disk
What problem are you trying to solve?
This is especially true on chromebook, it is quite random, but sometime when I come back and unlock my session, the process start logging "Audio output stream failed: a backend-specific error has occurred: alsa::poll() returned POLLERR" indefinitly (well unmutting the host sound make this disapears) but anyway the log size increase by 5Gb every minutes meaning the disk is full in a jiffy.
The log file with this issue is "github-app.{pid}.log".
Proposed solution
Would it be possible to limit the size of this file to let say 1Gb and make it rolling (keep 5 file maximum) + an alert "warning rolling log file, check why you have so many logs" .
Workflow impact
no need to clean file to continue working, warning on strange alert if there are.
Installation context
No response
Additional context
No response