You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disable filesystem timestamp resolution persistence to JGit config (#9)
When user.home resolves to a relative or invalid path (e.g. "?" on
JDK 8-18 in containers without a /etc/passwd entry for the running
UID), FileStoreAttributes.saveToConfig() creates a config file
inside the working directory. This pollutes the repository working
tree, and the file ends up in the LST manifest. On Windows, the "?"
character is illegal in paths, causing InvalidPathException when
processing the LST.
The in-memory FileStoreAttributes cache is sufficient for the
lifetime of a JVM process. The only cost of not persisting is
re-measuring filesystem timestamp resolution on the next JVM start,
which is fast.
0 commit comments