Git warning: "Empty last update token."

Question

What is the cause and resolution for the git warning message "Empty last update token."?

I have a repository, where every command prints this warning, e.g.

$ git status
warning: Empty last update token.
On branch foo
Your branch is up to date with 'origin/foo'.

$ git fetch
warning: Empty last update token.

$ git reset --hard
warning: Empty last update token.
Updating files: 100% (79/79), done.
HEAD is now at e1c42a2 blah

$ git prune
warning: Empty last update token.

The commands still seem to succeed. The warning message totally confuses external tools like git-extensions though, which shows "unresolved merge conflicts" when git status contains any unexpected output.

The problem only occurs with the local repository on one specific pc, but copying the .git folder to a different pc reproduces the problem.

I could delete the local copy and start fresh, but I would like to determine the cause, and perhaps even save the stashes.

user_453168 · Answer

This isn't a great answer, but it got rid of the error message for me:

Check if core.fsMonitor is on:

$ git config core.fsMonitor
true

And if true, turn it off:

$ git config core.fsMonitor false

$ git config core.fsMonitor
false

Potentially more information on this thread: https://public-inbox.org/git/4aa1293e-00b6-b9ef-efd4-cdf605db37a1@jeffhostetler.com/

user_186123 · Answer

@kaveman is right, this is evidently the new filesystem monitoring daemon that got built into git for Windows and Mac OS in 2.37. When I enabled with core.fsMonitor = true in my .gitconfig, git 2.35.1 printed this same Empty last update token warning. After I upgraded to git 2.37, the warning disappeared.

Git warning: "Empty last update token."

2 Answers