{"thread":{"id":"60633","subject":"Problem with commit-graph verify","startedAt":"2023-12-19T13:39:38Z","lastAt":"2023-12-19T13:39:38Z","messageCount":1,"participants":["Anton Sergeev"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"485813","messageId":"535d231b-3351-499d-abf0-b571dbd3c965@elecard.com","threadId":"60633","inReplyTo":null,"subject":"Problem with commit-graph verify","fromName":"Anton Sergeev","fromEmail":"anton.sergeev@elecard.com","sentAt":"2023-12-19T13:39:34Z","receivedAt":"2023-12-19T13:39:38Z","isPatch":false,"sender":{"key":"anton.sergeev@elecard.com","avatar":null},"body":"Hi folks,\n\nI have a problem with 'commit-graph verify' in poco repository ([1]).\nA commit appeared there with an odd timestamp and time zone ([2]):\n\n     git show --no-patch --pretty=%ai \n381ac1d9a82c9682a5046dd51802a687a81ace91\n     # 2106-02-07 06:28:18 -11309508\n\nThe main problem is that the 'commit-graph verify' return error:\n\n     git commit-graph write\n     git commit-graph verify\n     # commit-graph generation for commit \n1763a5017d8c0a9af6094fde91c43a5722bbde4c is 1699836629 < 4702109779\n     # Verifying commits in commit graph: 100% (9489/9489), done.\n\n     echo $?\n     # 1\n\nAnd this results in an error on fsck:\n\n     git fsck\n     # ...\n     # error in commit 381ac1d9a82c9682a5046dd51802a687a81ace91: \nbadTimezone: invalid author/committer line - bad time zone\n     # ...\n     # commit-graph generation for commit \n1763a5017d8c0a9af6094fde91c43a5722bbde4c is 1699836629 < 4702109779\n     # ...\n\n     echo $?\n     # 20\n\nI found that first error can be masked using 'fsck.skiplist' file. But \ncan't find how to mask the second.\nIs there a workaround for this case?\n\nSystem info:\n* git version: 2.43.0\n* OS: Debian GNU/Linux 11 (bullseye), x86_64\n\nNotes:\n* This error originally occurred on a local GitLab installation, that \nperiodically run fsck on all repos. And the poco repo mirror in our \nGitLab instance is now marked as failed.\n* Another strange thing about this commit is that git can't find any \nbelonging branch for it, but parent and child commits are has ones:\n\n     git log --pretty=format:\"%h %ad | %s%d [%an]\" --graph --date=short \n-n10 4261-move-autocommit-abstractsession\n     # ac7e39ff8 2023-11-14 | Fixed indentation in ci.yml \n(4261-move-autocommit-abstractsession) [Friedrich Wilckens]\n     # 543ea150a 2023-11-14 | Github workflow: re-activated \nlinux-gcc-make-postgres [Friedrich Wilckens]\n     # a2d10dffe 2023-11-13 | PostgreSQL SessionImpl: reuse autocommit \nflag of AbstractSessionImpl. [Friedrich Wilckens]\n     # d32f62031 2023-11-13 | MySQL SessionImpl: make sure autocommit \nmode is on when session is openend or reset. [Friedrich Wilckens]\n     # c919b7f79 2023-11-13 | chore(CI): re-enable mysql [Alex Fabijanic]\n     # ffd0007f2 2023-11-13 | fix(Data::AbstracSessionImpl): protect \nautocommit feature handlers #4261 [Alex Fabijanic]\n     # 1763a5017 2023-11-12 | Brought MySQL backend in line with \n_autoCommit flag of AbstractSessionImpl. [Friedrich Wilckens]\n     # 381ac1d9a 2106-02-07 | feat(Data::AbstractSessionImpl): add \nautoCommit property and tests #4261 [Alex Fabijanic] <---\n     # 18eea1bb7 2023-11-11 | temporarily comment failing mysql ci until \nfixed [Aleksandar Fabijanic]\n     # 6a5387ec2 2023-11-11 | add visitor pattern implementation for \nPoco::Dynamic::Var (#4144) [Alexander B]\n\n     for _c in 1763a5017 381ac1d9a 18eea1bb7; do\n       echo \"* $_c:\";\n       git branch --contains=$_c | sed 's/^/  /';\n     done\n     # * 1763a5017:\n     #     4261-move-autocommit-abstractsession\n     # * 381ac1d9a:\n     # * 18eea1bb7:\n     # \n2366-pocoprocesslaunch-unix-possible-memory-leak-when-launching-invalid-command\n     #     4261-move-autocommit-abstractsession\n     #     569-DateTimeParser-cherry-pick\n     #     devel\n\nLinks:\n[1]: https://github.com/pocoproject/poco\n[2]: \nhttps://github.com/pocoproject/poco/commit/381ac1d9a82c9682a5046dd51802a687a81ace91\n\n\n"}]}