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

Re: [PATCH 0/2] report lock error in write_index

From
Han Young <hanyang.tony@bytedance.com>
Date
May 21, 2025, 09:18 UTC
Message-ID
<CAG1j3zHUeGWQ-AD7bpJ=QBVAviBTcPi1yDRfM043+6sY4qkq9Q@mail.gmail.com>
In-Reply-To
<20250521083521.6552-1-hanyang.tony@bytedance.com>
On Wed, May 21, 2025 at 4:35 PM Han Young <hanyang.tony@bytedance.com> wrote:
> We can let repo_hold_locked_index print the error message if the locking
> failed.

One downside of this is the command still prints "could not write index" below the lock error. The caller can't distinguish between the lock failure and the the actual writing failure.

Previous: Han Young
Message 4 of 4 in “report lock error in write_index”
  1. 0/2 report lock error in write_indexHan Young, May 21, 2025
  2. 1/2 read-cache: report lock error when refreshing indexHan Young, May 21, 2025
  3. 2/2 read-cache: unify write index error messageHan Young, May 21, 2025
  4. Han YoungMay 21, 2025

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.