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

[PATCH v3 0/2] maintenance: improve lock acquisition failure handling

From
Pushkar Singh <pushkarkumarsingh1970@gmail.com>
Date
Nov 4, 2026, 17:34 UTC
Message-ID
<20261104173422.20725-1-pushkarkumarsingh1970@gmail.com>
In-Reply-To
<20261102122955.143018-2-pushkarkumarsingh1970@gmail.com>
Greetings,

This series improves how "git maintenance" handles failures to acquire the maintenance lock.

The first patch changes the handling of lock acquisition failures so that manual invocations report an error and return a non-zero exit status, while automatic invocations print a warning and exit successfully.

The second patch adds a Trace2 data event to make it easier to identify cases where automatic maintenance is repeatedly skipped due to lock acquisition failures.

Changes in v3:
- Split the changes into two separate patches: one for lock
  failure handling and another for Trace2 instrumentation.
- Use `strerror(err)` consistently for reporting lock acquisition
  failures in Trace2.
- Deduplicate the diagnostic message construction while preserving
  the distinction between warnings and errors.

Thanks, Pushkar

Pushkar Singh (2):
  maintenance: report lock acquisition failures
  maintenance: trace lock acquisition failures
Previous: Pushkar SinghNext: Pushkar Singh
Message 7 of 13 in “maintenance: trace when auto maintenance skips due to lock”
  1. maintenance: trace when auto maintenance skips due to lockPushkar Singh, Nov 1, 2026
  2. Patrick SteinhardtNov 2, 2026
  3. Pushkar SinghNov 2, 2026
  4. maintenance: improve handling of lock acquisition failuresPushkar Singh, Nov 2, 2026
  5. Patrick SteinhardtNov 2, 2026
  6. Pushkar SinghNov 3, 2026
  7. 0/2 maintenance: improve lock acquisition failure handlingPushkar Singh, Nov 4, 2026
  8. 1/2 maintenance: report lock acquisition failuresPushkar Singh, Nov 4, 2026
  9. 2/2 maintenance: trace lock acquisition failuresPushkar Singh, Nov 4, 2026
  10. 0/2 maintenance: improve lock acquisition failure handlingPushkar Singh, Nov 18, 2026
  11. 1/2 maintenance: handle lock acquisition failures correctlyPushkar Singh, Nov 18, 2026
  12. 2/2 maintenance: trace lock acquisition failuresPushkar Singh, Nov 18, 2026
  13. Aniket GuptaNov 4, 2026

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.