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

GIT_TRACE doesn't show content filter files it's operating on

From
SBStas Bekman <stas@stason.org>
Date
Aug 27, 2018, 23:23 UTC
Message-ID
<3fdc0c24-bbee-e7b3-ec43-7e926cee71e1@stason.org>
Hello,

I'm debugging the workings of a configured git content filter (nbstripout) and I'm trying to get GIT_TRACE to show me the files it's operating on, but it doesn't. Consider:

$ GIT_TRACE=1 git pull origin master [...] removed irrelevant sections of the output 16:49:28.846707 run-command.c:640 trace: run_command: git merge FETCH_HEAD 16:49:28.849309 git.c:344 trace: built-in: git merge FETCH_HEAD Updating 1ea49ad..ae0ba93 16:49:28.863291 run-command.c:640 trace: run_command: nbstripout 16:49:28.864700 run-command.c:640 trace: run_command: nbstripout 16:49:28.866060 run-command.c:640 trace: run_command: nbstripout [...] many more of the same

How can I get GIT_TRACE's run_command to show the arguments passed to the filter? I looked at various other debug environment variables in git's manual, but I don't see anything that would enable that level of debug.

I'm aware of git check-attr, but I'd like to see the run time trace on which files it's running the filter on and with which arguments.

git version 2.17.1

I originally posted this as a question here: <https://stackoverflow.com/questions/51995773/getting-git-to-show-specific-filenames-it-is-running-content-filters-on> and it appears that sq_quote_argv_pretty() doesn't get argv when a content filter is invoked, so it doesn't show this information.

Would it be possible to make the files and any other passed arguments show in the trace?

Thank you.
-- 
________________________________________________
Stas Bekman       <'))))><       <'))))><
https://stasosphere.com  https://chestofbooks.com
https://experientialsexlab.com https://stason.org
https://stasosphere.com/experience-life/my-books
Next: Jeff King
Message 1 of 6 in “GIT_TRACE doesn't show content filter files it's operating on”
  1. Stas BekmanAug 27, 2018
  2. Jeff KingAug 27, 2018
  3. Stas BekmanAug 28, 2018
  4. Jeff KingAug 28, 2018
  5. Stas BekmanAug 28, 2018
  6. Stas BekmanAug 28, 2018

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.