Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Installing with --source git because I want to work on SDODS itself. The clone appears to succeed and then:
The checkout is missing packages/cli — the clone looks incomplete.Exit code 7. ~/.sdods/app exists and has a .git directory in it, so something arrived.
Accepted answer
That check runs after the clone and asserts the tree actually contains what it needs, because a clone can exit zero and still leave you with a partial tree — a proxy that truncates a large transfer is the usual cause, and a mid-transfer network drop is the other.
Delete the directory and let it clone from scratch. Re-running on top of a broken checkout tries to fetch and check out again, which will not repair a tree that is missing files:
rm -rf ~/.sdods/app
curl -fsSL https://sdods.com/install.sh | sh -s -- --source git --verbose--verbose matters here: the clone output is hidden unless you ask for it, and if the transfer is being cut off the git error usually says so in a line you would otherwise never see.
If you are behind a proxy, also set git config --global http.proxy before retrying. And if you only want to use SDODS rather than work on it, drop --source git entirely — the default installs compiled packages and never clones anything.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.