Open mikefairbank opened 2 months ago
Hello Mike,
Thank you for taking the time to report the bug and providing the details. I appreciate your feedback, will investigate the issue, and work on a solution to the best of my ability. This is a nice report because the problem seems to be very clear and is quit easy to solve because of that.
If you have any more details to share, feel free to reach out.
Not sure when we'll find the time to work on it. Please see the projects background information to get an idea about our workflow andn priorities:
Best regards, Christian
This "bug" has mysteriously fixed itself. I think I might be wasting your time asking you to fix this one - maybe it was a problem with my own file system and some dodgy moving from one drive to another which I'd been doing. Here is the situation now:
So all working now. So if the code around leap-year Februaries, and smart remove looks fine, then please delete this issue. Sorry!
Thank you very much for reporting back. No problem. Sometimes magic happens. 😆 We have other issues around smart remove and need to improve the unit tests. I will take you leap years use case into account when improving the unit tests. So I keep the issue open.
Here is the problem (See image): Smart remove did not handle the data 2024-02-29. It has left many days from that month, when it was only meant to leave one day from that month.