git/list[1] front-page[2] threads[3] people[4] search[5] about
 

回复: RE: [External Mail]Re: Git fork process infinitely and never stop

From
程程洋 <chengyang@xiaomi.com>
Date
Jul 6, 2022, 14:03 UTC
Message-ID
<e071496cfdb04cce8eac322febb6af45@xiaomi.com>
In-Reply-To
<202207061520052718298@oschina.cn>
To lilinchao:
>So the repo "git/gerrit" is hosted in your local? and how you "copy" it to your own PC?
1. git/gerrit is hosted on remote server
               2. I just scp the whole repository of the user who reproduce the problem to our own PC. And then we can reproduce it on our own PC.
To Johannes:
> Hooks may also play a role.
We do have some hooks. But I don't think they're related. Because even I delete those hooks, the problem stands still
To Ævar Arnfjörð:
>I assume you can't share the repo, but perhaps try if you can reproduce it with a "git fast-export --anonymize" version of it, and if so whether you'd be willing to share that. It will publish the "shape of the history" of the repo, but not any meaningful data (all commits, trees, blobs etc. are replaced).
`git fast-export --anonymize` just output is empty. If I try `git fast-export --anonymize --all`, it seems to fetch first, which goes into the infinite loop again
>The YouTube video shows that you're using various options to git-fetch, including filters, refspecs etc. Does a plain "git fetch" reproduce this, and if not what's the option (try adding them one at a time &
>experiment) that needs to be added to trigger this?
`git fetch` also has this problem.

I somewhat suspect some --filter funny business, but that's just a hunch... It seems to happen after I told my team to use "partial-clone" AND "git v2.36.1". I'm not sure which one is the cause or both of them cause this. #/******本邮件及其附件含有小米公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件! This e-mail and its attachments contain confidential information from XIAOMI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!******/#

Previous: lilinchao@oschina.cnNext: 程洋
Message 7 of 14 in “Git fork process infinitely and never stop”
  1. 程洋Jul 4, 2022
  2. Bagas SanjayaJul 5, 2022
  3. 程洋Jul 5, 2022
  4. Ævar Arnfjörð BjarmasonJul 5, 2022
  5. Johannes SixtJul 6, 2022
  6. lilinchao@oschina.cnJul 6, 2022
  7. 回复: RE: [External Mail]Re: Git fork process infinitely and never stop程洋, Jul 6, 2022
  8. 程洋Jul 7, 2022
  9. 程洋Jul 8, 2022
  10. possible bug with commit-graph causing git to fork bomb (was Re: [External Mail]Re: Git fork process infinitely and never stop)Carlo Marcelo Arenas Belón, Jul 9, 2022
  11. Han XinJul 9, 2022
  12. Carlo ArenasJul 9, 2022
  13. 程洋Jul 11, 2022
  14. 程洋Sep 27, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.