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
{{ message }}
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
This is a bit odd. If Atom is running, with this package enabled, I can no longer run git rebase on the terminal. This is because apparently the package has held onto a Git lock:
fatal: Unable to create '/Users/gjtorikian/github/github/.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.
As this package doesn't support rebase -i, dropping to the terminal is the only way to achieve this. Is there anything that can be done for this?
@gjtorikian Hm, curious. If you edit ~/.atom/packages/github/lib/models/workdir-context.js and change the number 3000 on line 46 or so to something larger — say, 30000, does the problem persist?
Activity
BinaryMuse commentedon May 13, 2017
What's your current version? This should be fixed by #726, which fixed a very similar bug (#348).
BinaryMuse commentedon May 13, 2017
(You can use
git --git-dir ~/.atom/packages/github/.git rev-parse headto get this for now)gjtorikian commentedon May 13, 2017
I think my version is mega old. I'm on f897a4c.
gjtorikian commentedon May 13, 2017
Nope: I'm on ca87e37 now, and the problem persists. 😢
BinaryMuse commentedon May 15, 2017
@gjtorikian Hm, curious. If you edit
~/.atom/packages/github/lib/models/workdir-context.jsand change the number3000on line 46 or so to something larger — say,30000, does the problem persist?gjtorikian commentedon May 15, 2017
I'm having trouble reproducing it now, so I'm wondering if I just forgot to restart Atom.
Closing for now, then if it springs up again I'll try changing the timeout.
BinaryMuse commentedon May 15, 2017
Oooo that makes me feel a little better! 😅 Thanks!