https://bugs.kde.org/show_bug.cgi?id=404515
Bug ID: 404515
Summary: Interference from KDevelop while doing an interactive
git rebase
Product: kdevplatform
Version: 5.3.1
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: git
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
SUMMARY
An interactive rebase (for squashing commits) just failed on me because I had
the corresponding project open in KDevelop and directory changes were
apparently picked up that caused git activity.
STEPS TO REPRODUCE
1.
```
> git rebase -i 10d97998ded8817a610c50b764c83c71e4e46a06
```
OBSERVED RESULT
```
fatal: Unable to create '/path/to/.git/index.lock': File exists.
Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.
Could not apply aeabbf1b79... Nothing to be seen here
Exit 1
```
EXPECTED RESULT
No interference.
In particular, I'm not expecting KDevelop to run git commands each time a file
or directory change notification is received.
Or rather, if something is to fail I'd expect it to be in KDevelop's git query
because of the already started external git activity which triggered KDevelop's
reaction.
ADDITIONAL INFORMATION
I'm not entirely certain how realistic my expectation is... but I'm inclined to
think that it ought to be possible to obtain state (read-only) information from
a repository without the need for a lock file (= in such a way that it doesn't
interfere with externally triggered changes.
--
You are receiving this mail because:
You are watching all bug changes.
