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

Re: fatal: unable to read after commit - deeper analysis

From
KEKlaus Ethgen <klaus@ethgen.ch>
Date
Apr 13, 2019, 09:21 UTC
Message-ID
<20190413092136.GK12669@ikki.ethgen.ch>
In-Reply-To
<CAP8UFD0bBBtOOz9ew_2URCp3nY1v0_OHMby1-N+T0nCDW82DRg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,

I did a deep analysis of the problem and found that the trouble finally was caused of some change in git (I did not search, when this changed. But maybe you can tell me.)

Finally, the error was a combination of 4 tools, git, vim, the mentioned vim-addon and task with a task-hook for committing pending.data.

When I do a git commit which invokes vim, then the following variables
are set:
- - GIT_INDEX_FILE
- - GIT_AUTHOR_DATE
- - GIT_PREFIX
- - GIT_EXEC_PATH

And $GIT_INDEX_FILE is the source of trouble here. The task-hook clears respective sets the variables GIT_DIR and GIT_WORK_TREE. However, the GIT_INDEX_FILE environment is set (in some cases) to an absolute path pointing to .git/index.lock or .git/index (I have no idea when it is taking the .lock variant).

Now we have a mismatch of GIT_DIR and GIT_WORK_TREE on one hand and the absolute path of GIT_INDEX_FILE on the other. So the trouble is set. The following "git add pending.data" did break all. It does something to an index that does not belong to the git repo.

Mystery is when and why this changed in git. It was definitively changed in some recent version.

Regards
   Klaus
- -- 
Klaus Ethgen                                       http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16            Klaus Ethgen <Klaus@Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlyxqh8ACgkQpnwKsYAZ 9qxXWAv/QI6XeQ4H+Y39K3nLi68JLZo2/VzcI1CfVw42PeckxzxZHg1YUTXrr5Qk +bQ5drXcfzNMxWkCe1fh9CoHiyJyiAIPNfMjqiUaCB8881Ttr4SYd/lalvYVXPgt m0g7XO51Kh5LqPP6h7KcjBM0c6OSyQznE8Q6L0FSnDP4gCkBTW75AmxBytUk+sDq uOajtyOiOr1Fz1krn89VBaLJJPMVo+OInbNwetQUgOGIN7BsHsG68Ilwoimdlt+H 7sd5HJwVrQ/w9VdXzniLPznzkG4l/3YlU8IQWKR13dRFf68LrT1ZR+F4TJpjlm/Y l/KKF0EcVKbhuJ47gLIUDf3faeLFxdF1iOviKkJ0A0cfg5Z8M4ds8hBoiqhMSr+X 5fgINyhQfMurSTAuspZLJ0xjLu+Wv+h9Xt1jQZpW3YlPgi3O6Dn2K1V9ACaozP8G 0EIIMOvTNvqVw9iLe4a6cBm1M+gXfWRRf7H6wqvDhDuuSVF2h1sGwMMQHiumlqm3 au+0hEGQ =6ikc -----END PGP SIGNATURE-----

Previous: Klaus EthgenNext: Jeff King
Message 6 of 7 in “fatal: unable to read after commit”
  1. Klaus EthgenApr 11, 2019
  2. Christian CouderApr 12, 2019
  3. Klaus EthgenApr 12, 2019
  4. Klaus EthgenApr 12, 2019
  5. Klaus EthgenApr 12, 2019
  6. Klaus EthgenApr 13, 2019
  7. Jeff KingApr 22, 2019

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.