{"thread":{"id":"60783","subject":"Fatal error: commit-graph-chain.lock': File exists.","startedAt":"2024-01-23T15:27:31Z","lastAt":"2024-01-23T15:27:31Z","messageCount":1,"participants":["Thomas Braun"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"487262","messageId":"1015793055.437265.1706022071164@ox.hosteurope.de","threadId":"60783","inReplyTo":null,"subject":"Fatal error: commit-graph-chain.lock': File exists.","fromName":"Thomas Braun","fromEmail":"thomas.braun@virtuell-zuhause.de","sentAt":"2024-01-23T15:01:11Z","receivedAt":"2024-01-23T15:27:31Z","isPatch":false,"sender":{"key":"thomas.braun@virtuell-zuhause.de","avatar":"https://avatars.githubusercontent.com/u/1185677?v=4"},"body":"Hi,\n\nSince 2.43.0 I'm seeing the following error message when I fetch from a remote:\n\n$LC_ALL=C git fetch --all\nremote: Enumerating objects: 446, done.\nremote: Counting objects: 100% (446/446), done.\nremote: Compressing objects: 100% (135/135), done.\nremote: Total 446 (delta 328), reused 415 (delta 311), pack-reused 0\nReceiving objects: 100% (446/446), 432.84 KiB | 1.01 MiB/s, done.\nResolving deltas: 100% (328/328), completed with 29 local objects.\nFrom EEE:XXX/YYY\n * [new branch]          bugfix/ZZZ -> origin/ZZZ\n * [new branch]          bugfix/ZZZ -> origin/bugfix/ZZZ\n + 7244c9b68...6dad36582 feature/AAA -> origin/feature/AAA  (forced update)\n + 7ce96b207...7bee890d6 feature/BBB -> origin/feature/BBB  (forced update)\n * [new branch]          feature/CCC -> origin/feature/CCC\n   fd8c36a84..2ab4db03d  main                                            -> origin/main\nfatal: Unable to create '/DDD/.git/objects/info/commit-graphs/commit-graph-chain.lock': File exists.\n\nAnother git process seems to be running in this repository, e.g.\nan editor opened by 'git commit'. Please make sure all processes\nare terminated then try again. If it still fails, a git process\nmay have crashed in this repository earlier:\nremove the file manually to continue.\n\nObservations:\n- repo and gitforge independent\n- only happens when fetch.writeCommitGraph is turned on\n- git gc cleans up the stale lock file\n- I think this is only happening when multiple branches on the remote have changed\n\nI do have protocol.version set to 2.\n\nI tried replicating the issue with an example but failed so far.\n\nDoes that ring a bell somewhere? Where should I start poking?\n\nThanks,\nThomas\n\n[System Info]\ngit Version:\ngit version 2.43.0\ncpu: x86_64\nbuilt from commit: 564d0252ca632e0264ed670534a51d18a689ef5d\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nuname: Linux 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64\nCompiler Info: gnuc: 12.2\nlibc Info: glibc: 2.36\n$SHELL (typically, interactive shell): /bin/bash\n"}]}