search

airbnb / knowledge-repo

A next-generation curated knowledge sharing platform for data scientists and other technical professions.
Apache License 2.0
5.48k stars 688 forks source link

knowledge_repo script cannot connect to remote git repo #368

Open pottegil opened 6 years ago

pottegil commented 6 years ago

I've setup the knowledge_repo application, initialized a repo, then performed a successful git push origin master. When I check the files on the gitlab server, the initial commit and push is there.

I use the export $KNOWLEDGE_REPO = PATH environmental variable

However, now overtime I run a knowledge_repo command I get:

WARNING:knowledge_repo.repositories.gitrepository:Cannot connect to remote repository hosted on gitlab.server.com. Continuing locally with potentially outdated code.
Created a Rmd knowledge post template at ./documents/example_tableau.Rmd.

I get the same error message when I launch the service, or try to do anything. Whenever I try to use the knowledge_repo commands to commit and merge files, they all fail with the same error message: WARNING:knowledge_repo.repositories.gitrepository:Cannot connect to remote repository hosted on gitlab.server.com. Continuing locally with potentially outdated code.

If I manually git push and merge, then the posts show on the server. Any ideas?

Auto-reviewers: @NiharikaRay @matthewwardrop @earthmancash @danfrankj

matthewwardrop commented 6 years ago

@pottegil Hi Gill,

Sorry for the long lead time on this (I've been on paternity leave... just back).

How do you connect to the git repository manually? Do you use SSH keys, or manually type passwords? Is the knowledge repo running in the same shell environment as your manual git efforts?

tehshane commented 6 years ago

Not OP, but having the same issue here. We use SSH keys to connect to GitHub, and running ssh git@github.com shows we're connecting and authenticating successfully. Running knowledge_repo --repo test-knowledge-repo/ runserver yields the error shown by @pottegil.

We're running Knowledge Repo on an AWS EC2 instance, and it's in the same shell environment as we run git in.

Anything we can use to troubleshoot further?