search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.89k stars 1.23k forks source link

Pushing to a git repo fails - worktree should be provided #18300

Open avioli opened 5 years ago

avioli commented 5 years ago 

> ls -la
drwxr-xr-x   - avioli  9 Jul 10:50 .git
.rw-r--r-- 150 avioli  9 Jul 10:11 docker-compose.yaml
.rw-r--r-- 260 avioli  9 Jul 10:09 Dockerfile
.rw-r--r-- 184 avioli  9 Jul 10:28 Home.md
.rw-r--r--  32 avioli  9 Jul  9:45 readme.md

> keybase git create --team=stamatovs wiki
Repo created! You can clone it with:
  git clone keybase://team/stamatovs/wiki
Or add it as a remote to an existing repo with:
  git remote add origin keybase://team/stamatovs/wiki

> git remote add origin keybase://team/stamatovs/wiki

> git push -u origin master
Initializing Keybase... done.
Syncing with Keybase... This operation conflicted with another operation on the server, or it took too long. Please try again.
git-remote-keybase error: (1) This operation conflicted with another operation on the server, or it took too long. Please try again.

> git push -u origin master
Initializing Keybase... done.
Syncing with Keybase... worktree should be provided
git-remote-keybase error: (1) worktree should be provided

> git push -u origin master
Initializing Keybase... done.
Syncing with Keybase... worktree should be provided
git-remote-keybase error: (1) worktree should be provided

> keybase --version
keybase version 4.1.0-20190612165948+952fee6c59

my log id: 63151da48f044a9354c5fd1c

strib commented 5 years ago

Thanks for the report. I see the issue, it's a bug in our code triggered by a slower-than-expected connection to one of our servers from your client. I'll fix the bug on our end.

On your end, you should be able to fix it by deleting the repo with keybase git delete, and then recreating it. If you don't get the "This operation conflicted" error again, you should be good to go. Sorry for the inconvenience!