Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git push failing with "git-remote-keybase error: (1) Server: block does not exist" #11358

Open
ORBAT opened this issue Apr 11, 2018 · 1 comment
Labels

Comments

@ORBAT
Copy link

ORBAT commented Apr 11, 2018

I had a git push get stuck (noticed it after a minute or so.) I killed the git process and tried again, but now the result is always

Initializing Keybase... done.
Syncing with Keybase... Server: block does not exist
git-remote-keybase error: (1) Server: block does not exist

my log id: 6c6d207293939d1a120cdb1c

@strib strib added the acked label Apr 11, 2018
@strib
Copy link
Contributor

strib commented Apr 11, 2018

It seems like the root cause of the issue happened on March 30th, before the macOS release that contains the fix for an issue with a similar symptom: keybase/kbfs#1513.

So my best guess is you hit the same bug (maybe the same as #10816 as well).

Do you have an up-to-date local copy of this repo (with all branches, etc)? If so, the easiest thing is probably the delete the repo with keybase git delete <reponame> or in the GUI, and then recreate it and push to it from your local copy.

After you do that, you might find that git commands start failing with the same error after a little while -- in that case, please do another keybase log send and I can help you get rid of it permanently.

If you can't restore the repo on your own, I can work with you to restore the data on our servers, but it'll take some time and some back-and-forth. But happy to do it if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants