On Fri, Jul 08, 2022 at 10:45:08AM +0000, 程洋 wrote: > Any feedback on this? My guess is that the problem has been difficult enough to reproduce with the instructions you provided and because of the top posting that the people most likely to come up with a solution are not even aware yet of the issue. I changed the subject and I am including some of your discovery below and copying someone that might know better, but trying to find a way to provide a repository where this could be replicated locally (maybe using the --anonymize option mentioned in the thread) or a copy of the repository (not in an attachment) if it is not sensitive would be of a lot of help. Also, I heard rumours that most of the people working with that feature that you might have identified as problematic might be off this week, so might need to wait a little longer. Carlo PS. also, try to post your responses inline like this one. ------ CUT BELOW FOR PROBABLY RELEVANT INFORMATION FROM THREAD ------ Stolee > To be a supplement. > If I delete .git/objects/info/commit-graph, everything works well As well as fetch with `-c core.commitGraph=false` This would seem to indicate that something in the repository might be triggered by the commit-graph code. > if I execute `git fetch --filter=blob:none --quiet --progress miui --prune --tags +refs/heads/*:refs/remotes/miui/* +refs/heads/miui13-s-thor-vendor-stable:refs/remotes/miui/miui13-s-thor-vendor-stable` on version 2.25.1. It just throw error rather than infinite loop, like this youtube video "https://www.youtube.com/watch?v=qvYTvVRE0FU&feature=youtu.be"; maybe a regression? Carlo
