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
Currently Stump generates/appends to a single log file and has no logic for automatically cleaning it up. There are API endpoints and other utility functions around wiping the log file, but I think it would be quite easy and less hassle to introduce rolling log. On a memory constrained machine, if someone were to set a verbose log level, this could easily OOM for a very actively used server
The text was updated successfully, but these errors were encountered:
Currently Stump generates/appends to a single log file and has no logic for automatically cleaning it up. There are API endpoints and other utility functions around wiping the log file, but I think it would be quite easy and less hassle to introduce rolling log. On a memory constrained machine, if someone were to set a verbose log level, this could easily OOM for a very actively used server
The text was updated successfully, but these errors were encountered: