Bug 270448

Summary: devel/gitqlient: .git/index.lock exists after closing the application
Product: Ports & Packages Reporter: Graham Perrin <grahamperrin>
Component: Individual Port(s)Assignee: Adriaan de Groot <adridg>
Status: Closed Unable to Reproduce    
Severity: Affects Only Me CC: freebsd, grahamperrin
Priority: --- Flags: bugzilla: maintainer-feedback? (adridg)
Version: Latest   
Hardware: Any   
OS: Any   

Description Graham Perrin freebsd_committer freebsd_triage 2023-03-25 19:12:37 UTC 
After each of my first two uses of the application, working with /usr/doc then long after closing, this (for example): 

% git -C /usr/doc reset --hard HEAD
fatal: Unable to create '/usr/doc/.git/index.lock': File exists.

… etc.

Should I report upstream? (<https://github.com/francescmm/GitQlient/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+index.lock> finds nothing.)
Comment 1 Mina Galić freebsd_triage 2023-03-25 19:37:22 UTC 
(In reply to Graham Perrin from comment #0)
yes please do
Comment 2 Adriaan de Groot freebsd_committer freebsd_triage 2023-03-27 23:30:43 UTC 
Can't reproduce, though (with an arbitrary local git repo, although all I do is start the application, open a repo, and then close the application): can you give me some steps to reproduce?
Comment 3 Graham Perrin freebsd_committer freebsd_triage 2023-04-13 05:16:34 UTC 
I can reproduce existence of the remnant, however I don't yet have reproducible steps. 

It will take some time for me to make things reproducible, shall we close this bug in the meantime? With an assumption that it might be fixable upstream.
Comment 4 Adriaan de Groot freebsd_committer freebsd_triage 2023-04-13 19:30:34 UTC 
It's worth filing upstream (nothing open there related to stray lock files, though). The thing I can imagine is this:
- some git operation is running
- gitqlient exits
- .. and kills the git process that is doing the work (or rudely interrupts the thread doing the work, I don't know about internals)

You can sort-of mimic the issue by killing git at an inconvenient time in a large repo (e.g. docs .. maybe that's my problem, that I'm working with too-small repos). I don't have any creativity for using this app, though -- so I need something like a scenario, after all. Even if it's not entirely reproducible, knowing where to click (other than the "close window" button) to use the application realistically would help.
Comment 5 Adriaan de Groot freebsd_committer freebsd_triage 2023-07-14 09:00:55 UTC 
Closing for now with "unable to reproduce"