tree 6996ea16ee2f098cb095f7c1b34ace09e82167e0
parent eec9b55dcf8fc08f431f16eaf139ab009453d445
author Thomas Wolf <thomas.wolf@paranor.ch> 1597956193 +0200
committer Thomas Wolf <thomas.wolf@paranor.ch> 1597993206 +0200

FS: write to JGit config in a background thread

Otherwise locking problems may ensue if the JGit config itself is
on a different file system. Since the internal is already updated,
it is not really important when exactly the value gets persisted.
By queueing up separate Runnables executed by a single thread we
avoid concurrent write access to the JGit config, and nested calls
to getFileStoreAttributes(Path) result in serialized attempts to
write.

The thread for writing the config must not be a daemon thread. If
it were, JVM shutdown might kill it anytime, which may lead to
the config not being written, or worse, a config.lock file being
left behind.

Bug: 566170
Change-Id: I07e3d4c5e029d3cec9ab5895002fc4e0c7948c40
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>