Good day, I encountered some weird behaviour that I think is a bug. I'll paste the bug report below and also attach it to this email. Best regards Sarah Gastner Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) I used the command "git log --after=2023-03-10 before=2024-01-24" in the kubernetes repository (https://github.com/kubernetes/kubernetes), checked out branch master (commit cb93d6ee69b8d4ca8701336e4f7cb278751f34e4). What did you expect to happen? (Expected behavior) The following commit (amongst others) to appear in the output: commit 501976cc34ed3bfea6e1c994d41cb9bc464d6c3b Author: Jiahui Feng <jhf@xxxxxxxxxx> Date: Mon Mar 13 14:40:47 2023 -0700 fix broken tests after dependency injection. What happened instead? (Actual behavior) The commit did not appear. What's different between what you expected and what actually happened? Both the author date and the commit date are 2023-03-13. The interval 2023-03-10 to 2024-01-24 should include this date and therefore this commit. Anything else you want to add: I was able to figure out the minimal date interval needed for this commit to appear: 2023-03-07 to 2023-03-14. The following command will only display the commit specified above: git log --after=2023-03-07 --before=2023-03-14 --grep="fix broken tests after dependency injection." If you change the --after date to one day later (2023-03-08), there will be no output. This issue appears in other repositories too. I observed this behaviour on Windows and WSL (Ubuntu). Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.47.1.windows.1 cpu: x86_64 built from commit: 2cd22437f64229935dc564db969cbcbfed5e9045 sizeof-long: 4 sizeof-size_t: 8 shell-path: D:/git-sdk-64-build-installers/usr/bin/sh feature: fsmonitor--daemon libcurl: 8.11.0 OpenSSL: OpenSSL 3.2.3 3 Sep 2024 zlib: 1.3.1 uname: Windows 10.0 19045 compiler info: gnuc: 14.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks]
Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) I used the command "git log --after=2023-03-10 before=2024-01-24" in the kubernetes repository (https://github.com/kubernetes/kubernetes), checked out branch master (commit cb93d6ee69b8d4ca8701336e4f7cb278751f34e4). What did you expect to happen? (Expected behavior) The following commit (amongst others) to appear in the output: commit 501976cc34ed3bfea6e1c994d41cb9bc464d6c3b Author: Jiahui Feng <jhf@xxxxxxxxxx> Date: Mon Mar 13 14:40:47 2023 -0700 fix broken tests after dependency injection. What happened instead? (Actual behavior) The commit did not appear. What's different between what you expected and what actually happened? Both the author date and the commit date are 2023-03-13. The interval 2023-03-10 to 2024-01-24 should include this date and therefore this commit. Anything else you want to add: I was able to figure out the minimal date interval needed for this commit to appear: 2023-03-07 to 2023-03-14. The following command will only display the commit specified above: git log --after=2023-03-07 --before=2023-03-14 --grep="fix broken tests after dependency injection." If you change the --after date to one day later (2023-03-08), there will be no output. This issue appears in other repositories too. I observed this behaviour on Windows and WSL (Ubuntu). Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.45.1.windows.1 cpu: x86_64 built from commit: 965b16798dab6962ada5b0d8cf0dca68f385c448 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19045 compiler info: gnuc: 13.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks]
Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) I used the command "git log --after=2023-03-10 before=2024-01-24" in the kubernetes repository (https://github.com/kubernetes/kubernetes), checked out branch master (commit cb93d6ee69b8d4ca8701336e4f7cb278751f34e4). What did you expect to happen? (Expected behavior) The following commit (amongst others) to appear in the output: commit 501976cc34ed3bfea6e1c994d41cb9bc464d6c3b Author: Jiahui Feng <jhf@xxxxxxxxxx> Date: Mon Mar 13 14:40:47 2023 -0700 fix broken tests after dependency injection. What happened instead? (Actual behavior) The commit did not appear. What's different between what you expected and what actually happened? Both the author date and the commit date are 2023-03-13. The interval 2023-03-10 to 2024-01-24 should include this date and therefore this commit. Anything else you want to add: I was able to figure out the minimal date interval needed for this commit to appear: 2023-03-07 to 2023-03-14. The following command will only display the commit specified above: git log --after=2023-03-07 --before=2023-03-14 --grep="fix broken tests after dependency injection." If you change the --after date to one day later (2023-03-08), there will be no output. This issue appears in other repositories too. I observed this behaviour on Windows and WSL (Ubuntu). Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.47.1.windows.1 cpu: x86_64 built from commit: 2cd22437f64229935dc564db969cbcbfed5e9045 sizeof-long: 4 sizeof-size_t: 8 shell-path: D:/git-sdk-64-build-installers/usr/bin/sh feature: fsmonitor--daemon libcurl: 8.11.0 OpenSSL: OpenSSL 3.2.3 3 Sep 2024 zlib: 1.3.1 uname: Windows 10.0 19045 compiler info: gnuc: 14.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks]
