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
I am using time rotating file handler that roll over at midnight to create new log file every day.
With the backup_count set, I've noticed that when the backup files reached the setting value, the oldest file is not being deleted instead the latest rolled over file is been deleted.
I am using time rotating file handler that roll over at midnight to create new log file every day.
With the backup_count set, I've noticed that when the backup files reached the setting value, the oldest file is not being deleted instead the latest rolled over file is been deleted.
aiologger/aiologger/handlers/files.py
Lines 393 to 414 in 385a863
Upon checking the code in get_files_to_delete method.
The last part of the method returns the files that exceeds backup_count to be delete.
The reversed descending sort gives the wrong result and latest log file is being deleted.
Possible fix is remove reverse=True so the result list is in ascending sort.
Not sure if anyone else is having this issue.
My environment is Debian 11 with python 3.9.2 and aiologger 0.7.0 release.
The text was updated successfully, but these errors were encountered: