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

Cannot Complete Install - Troubleshooting #776

Open
KarolinePurpleCarrot opened this issue Jul 19, 2023 · 1 comment
Open

Cannot Complete Install - Troubleshooting #776

KarolinePurpleCarrot opened this issue Jul 19, 2023 · 1 comment

Comments

@KarolinePurpleCarrot
Copy link

KarolinePurpleCarrot commented Jul 19, 2023

I am using CMD.exe Prompt to install into a local virtual environment; I am able to run the initial install (pip install --upgrade "knowledge-repo[all]"). It fails to run when I write the next prompt (knowledge_repo --repo test_repo init). My error reads: "'knowledge_repo' is not recognized as an internal or external command, operable program or batch file."

I have checked the pip list and "knowledge-repo" is present in the list.

Under my environment\Scripts there is a "knowledge_repo" file, but it does not look like an exe, it's just a txt file; I am also able to execute "setx KNOWLEDGE_REPO" and point it to my github repo on my local.

Also, if I open the knowledge_repo file in a code editor and run it, I get an error: ImportError: Bad git executable.

I am by no means a developer - just a data analyst trying to get this set up. Is there additional troubleshooting documentation somewhere or is something weird going on? Thank you!

@Tom271
Copy link

Tom271 commented Mar 15, 2024

Hi @KarolinePurpleCarrot, did you get anywhere with this? I think it's a Windows problem, this version runs fine on Mac. I have a similar problem on my Windows machine, except I don't get any error, the command just silently fails.

After having a bit more of a look, it seems that it is no longer supported on Windows? The github actions jobs only check macos and ubuntu. A possible workaround is to roll back to v0.8.8, but that requires dealing with a few dependency issues (namely in werkzeug and markdown). More of a headache than I thought.

There might be a more recent version than v0.8.8 that works, but I've not had time to test

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

No branches or pull requests

2 participants