Skip to main content

Troubleshooting and clean-machine FAQ

What was tested. On 2026-11-08 the sponsor unzipped olip-1.0-kit.zip into an empty folder on Linux and ran npm install, npm start, npm run walkthrough, the conformance suite against both endpoints, and the read-only example. Node.js 22 and Python 3.13. macOS and Windows have not been tested yet.

ProblemFix
cd: olip-0.2-…: No such file or directoryThe 1.0 kit unpacks to olip-1.0. Older copies of the quickstart named an earlier folder.
node: command not found or a syntax errorInstall Node.js 20 or later and check with node --version.
EADDRINUSE on port 8787Something else uses the port. Start on another one: PORT=8790 npm start (macOS, Linux) or $env:PORT=8790; npm start (Windows PowerShell), and pass the same port to --base.
PORT=8788 python3 ... fails on WindowsIn PowerShell: $env:PORT=8788; python alt-python/olip_alt_server.py
Python endpoint skips 6 checksExpected: A2A is optional and the Python endpoint implements Part 1 only, so its five Part 2 checks are skipped.
npm install is blocked by a proxyThe kit's only dependencies are ajv and ajv-formats (for schema validation). The endpoints themselves need none.
A downloaded file's SHA-256 does not matchDownload it again from Downloads. Kit zips are built reproducibly, so the same version always has the same hash.
Anything that looks like a real lawyer or clientStop and report it. The kit holds fictional data only.

Nothing in the kit needs an account, a key, a payment or any sponsor service.