Re: [PATCH 2/7] commit-graph: fix ordering bug in generation numbers

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 25, 2022, 17:35 UTC
Message-ID: <xmqqwnhietnz.fsf@gitster.g>
In-Reply-To: <756fd005-637d-a067-9949-e87fc15b3bf6@github.com>

Derrick Stolee <derrickstolee@github.com> writes:

Show 13 quoted lines

> It is very subtle, which is why it took me a while to debug this
> issue once I managed to trigger it.
>
>>     for each commit ctx->commits.list[i]:
>>         continue if generation number has been computed for it already
>
> This is the critical line in the current version. This includes
> "continue if the generation number was loaded from the previous
> commit-graph file." This means we under-count when building from
> an existing commit-graph with overflows.
>
> If we insert an increment here, then we risk double-counting. I
> should have described this better.

Ah, that obviously I missed.  Thanks.

$ 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.