Bug Description
graphify cluster-only <path> fails to label communities and falls back to Community N placeholders with a JSON decode error.
Steps to Reproduce
- Install graphify on Windows/Hermes:
pip install graphifyy && graphify install --platform hermes
- Use a corpus with mixed code + 1 doc file and set a working LLM key, e.g.:
export GOOGLE_API_KEY=...
graphify "H:/path/to/small-project"
- Run:
graphify cluster-only "H:/path/to/small-project"
Expected Behavior
All communities are labeled with meaningful names and the report is generated.
Actual Behavior
[graphify label] batch 1/1 (6 communities) failed: Expecting value: line 1 column 6 (char 5)
[graphify label] warning: community labeling failed (Expecting value: line 1 column 6 (char 5)); using Community N placeholders.
GRAPH_REPORT.md is still written, but all community names remain Community N.
Environment
- OS: Windows 10
- Shell: Git Bash / MSYS2
- graphify:
0.9.6
- Hermes: installed via
graphify install --platform hermes
- LLM backend: gemini via
GOOGLE_API_KEY / --backend
Notes
Bug Description
graphify cluster-only <path>fails to label communities and falls back toCommunity Nplaceholders with a JSON decode error.Steps to Reproduce
pip install graphifyy && graphify install --platform hermesexport GOOGLE_API_KEY=...graphify "H:/path/to/small-project"graphify cluster-only "H:/path/to/small-project"Expected Behavior
All communities are labeled with meaningful names and the report is generated.
Actual Behavior
GRAPH_REPORT.mdis still written, but all community names remainCommunity N.Environment
0.9.6graphify install --platform hermesGOOGLE_API_KEY/--backendNotes
cluster-onlyon the existing graph still reproduces the JSON parse failure.graphify install --platform hermesinstalls skill to wrong directory on Windows #1403 was fixed for Windows install path; this appears unrelated.