Describe the bug
After update to 2.7 I'm having problem with my log_filename.
After 21h (for me) is created a log_filename in a wrong way.
Is cretead a new_name with the tomorrow date.
To Reproduce
Steps to reproduce the behavior:
Start monitoring.
Wait to next autosaved log after 21 o'clock
Read the log_file, and see a current logfile_name (with tomorrow's date) with a new registry with a today's date.
Screenshots
Below the log created at 2021-12-03 after 21:00 (but filled with regristries from 02-December)
If I want to search for things happend on 02 December, I need to go to another file (created one day ago).
Below the log created at 2021-12-02before (yet) 21:00 (filled with OK regristries)).
If you realize here, the registries in both log files are the same (and that is ok). the file_name is a little bit different, because the "seconds" in the file_name.
Below the log created at 2021-12-03 after 21:00 (but filled with regristries from 01-December)
If I want to search for things happened after 21:00 at 02 December, the next log shows me things from December first.
Desktop (please complete the following information):
OS: [Ubuntu]
Browser [Chrome]
Version [96.0.4664.45 - 64bits]
Additional context
idk if I was clear here, but the problem occurs after 21:00 in auto saved in 10min (my default usage for guarantee ).
Maybe is related with my timezone, idk.
I'm writing this (open the bug issue ) at December, 5.
My recent created logfile now its named by whatsapp-monitor_2021-12-06&&22_41_12.csv.
It will happens after 23:59 (tomorrow):
A new logfile will be created with a name "_standardprefix-06&&00_01_12.csv.
About the regristries: Everything will be fine after that, until "_standardprefix-06&&20_51_12.csv.
About the file name log: when order by name the file will be created after "_standardprefix-05&&23_51_12.csv. and will be more dificult to find things happened.
Describe the bug After update to 2.7 I'm having problem with my log_filename.
After 21h (for me) is created a log_filename in a wrong way. Is cretead a new_name with the tomorrow date.
To Reproduce Steps to reproduce the behavior:
Screenshots Below the log created at 2021-12-03 after 21:00 (but filled with regristries from 02-December)![image](https://user-images.githubusercontent.com/47780282/144773046-19ec154a-bf04-4e04-8ae1-5531d86f64ad.png)
If I want to search for things happend on 02 December, I need to go to another file (created one day ago). Below the log created at 2021-12-02 before (yet) 21:00 (filled with OK regristries)). If you realize here, the registries in both log files are the same (and that is ok). the file_name is a little bit different, because the "seconds" in the file_name.![image](https://user-images.githubusercontent.com/47780282/144773176-161049bd-2e4f-42b9-809a-f5fcb2328f6b.png)
Below the log created at 2021-12-03 after 21:00 (but filled with regristries from 01-December) If I want to search for things happened after 21:00 at 02 December, the next log shows me things from December first.![image](https://user-images.githubusercontent.com/47780282/144773495-7315585b-f2b8-4414-8a54-9dc280999bec.png)
Desktop (please complete the following information):
Additional context
idk if I was clear here, but the problem occurs after 21:00 in auto saved in 10min (my default usage for guarantee ). Maybe is related with my timezone, idk.
I'm writing this (open the bug issue ) at December, 5. My recent created logfile now its named by whatsapp-monitor_2021-12-06&&22_41_12.csv. It will happens after 23:59 (tomorrow): A new logfile will be created with a name "_standardprefix-06&&00_01_12.csv. About the regristries: Everything will be fine after that, until "_standardprefix-06&&20_51_12.csv. About the file name log: when order by name the file will be created after "_standardprefix-05&&23_51_12.csv. and will be more dificult to find things happened.