how to contribute debugging

Debugging

Most Lode issues are easiest to debug by checking the SQLite data directory, rerunning a focused index, and inspecting JSON output from the CLI or daemon.

Useful commands

uv run lode status --json
uv run lode search "query" --json
uv run lode symbol "Name" --json
uv run lode neighbors NODE_ID --json
uv run lode impact TARGET --json

These commands are implemented in src/lode/cli.py and read from the data directory computed by src/lode/config.py.

Common symptoms

Symptom	Likely area	What to inspect
File missing from results	src/lode/indexer.py	SOURCE_EXTENSIONS, EXCLUDED_DIRS, generated-file checks
Symbol exists but does not resolve	src/lode/graph.py	import bindings, call details, duplicate local names
Search returns no hits	src/lode/storage.py	FTS rows in node_fts, repo filter, query spelling
Daemon returns 400	src/lode/daemon.py	request body, required fields, JSON decoding
Logs expose sensitive names	src/lode/observability.py	SENSITIVE_PARTS and sanitize()

Daemon diagnostics

Run the daemon locally and call health, status, and metrics:

LODE_FEATURE_METRICS=1 uv run loded --host 127.0.0.1 --port 7979
curl http://127.0.0.1:7979/health
curl http://127.0.0.1:7979/status
curl http://127.0.0.1:7979/metrics

Related pages

• How to monitor
• Daemon endpoints
• Configuration