-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fs-watcher][git] Filter the .git/index.lock
from the file changes
#1769
Comments
kittaakos
added
quality
issues related to code and application quality
git
issues related to git
labels
Apr 24, 2018
Git
CC: @svenefftinge |
kittaakos
pushed a commit
that referenced
this issue
Aug 1, 2018
kittaakos
pushed a commit
that referenced
this issue
Aug 1, 2018
kittaakos
pushed a commit
that referenced
this issue
Aug 1, 2018
marcdumais-work
pushed a commit
to marcdumais-work/theia
that referenced
this issue
Oct 15, 2018
So that a `git status` call will not end up in a index.lock file change. The `--no-optional-locks` is enabled by default for > 2.15.0 Git. Earlier Git versions are uneffected. Closes eclipse-theia#1769. Signed-off-by: Akos Kitta <kittaakos@typefox.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, each tracked Git repository is checked (via the
git status
command) whether there were any changes or not. This happens periodically (5 seconds) on the backend.git status
create a newindex.lock
file. AFAIK, it should happen only when the performed Git command edits the index.git status
should not. Seegit --no-optional-locks status
.git/index.lock
file changes?Currently, it does not cause any issues/side-effects.
The text was updated successfully, but these errors were encountered: