search

kejadlen / git-together

Better commit attribution while pairing without messing with your git workflow.
MIT License
158 stars 19 forks source link

Occasional failure to swap committer/sign-offer #9

Open alidaka opened 7 years ago

alidaka commented 7 years ago

Experienced on Windows 10 with git-together release 11.

Seems to be intermittent--usually works, and this is after the commit;

 2017-04-19 16:32:50 ☆  EUROPA-WIN10 in /mnt/c/Users/pivotal/workspace/<snip>
± md+al |benchmark S:1 ✗| → git commit -m "Add <snip>"
[benchmark 0272f8c] Add <snip>
 Author: <snip>
warning: CRLF will be replaced by LF in benchmark/benchmark.ps1.
The file will have its original line endings in your working directory.
 1 file changed, 24 insertions(+)
 create mode 100644 benchmark/benchmark.ps1
error: error setting git config 'git-together.active': 'al+md'
caused by: [2/-1] failed to rename lockfile to '/mnt/c/Users/pivotal/workspace/<snip>/.git/config': Permission denied

 2017-04-19 16:33:04 ☆  EUROPA-WIN10 in /mnt/c/Users/pivotal/workspace/<snip>
± md+al |benchmark ✓| →
kejadlen commented 7 years ago

Looks like an issue w/locking the git repo, but since this runs after the git commit command does, I'm not sure what recourse we have besides adding a retry w/backoff...

alidaka commented 7 years ago

Bummer. Is that what other tools do? Or is the way we're running just uncommon?

On Jun 5, 2017 07:26, "Alpha Chen" notifications@github.com wrote:

Looks like an issue w/locking the git repo, but since this runs after the git commit command does, I'm not sure what recourse we have besides adding a retry w/backoff...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kejadlen/git-together/issues/9#issuecomment-306201310, or mute the thread https://github.com/notifications/unsubscribe-auth/ALmUbmmnmHFjocL17zRG6FzCjrRUE8iKks5sBBAggaJpZM4NCXko .