README THREAD_PALETTE_PATH points to non-existent file #23

New issue

Closed

opened 2026-09-08 19:08:10 +00:00 by Mark · 0 comments

Mark commented

2026-09-08 19:08:10 +00:00

Owner

README THREAD_PALETTE_PATH points to non-existent file

Repo: Mark/easystitch-service
Severity: Medium — service appears non-functional out of the box
Found: 2026-09-08 full shakedown

Symptom

README §Configuration documents:

THREAD_PALETTE_PATH — Default: /data/brother_pr10.json

But that file doesn't exist in this repo, the engine repo, or anywhere on the filesystem.
Following the README literally produces a broken service:

GET /v1/threads/catalog  ->  {"catalog": []}
POST /v1/threads/resolve ->  {"error": "catalog_unavailable"}  (HTTP 503)

The correct path is /home/b/Projects/easystitch-service/data/brother_pr10.json
(62-thread, 3.5KB catalog that ships in this repo).

Why there are two catalogs

Mark/easystitch-service/data/brother_pr10.json — 62 threads (the one the service uses)
Mark/easystitch/src/embroidery_converter/thread_catalogs/brother_pr10_polyneon.json — 459 lines,
richer, but the service doesn't reference it

It's unclear which is canonical for production.

Fix

Update README to default THREAD_PALETTE_PATH to a real path the repo ships with
Or commit the catalog at /data/brother_pr10.json if the absolute path is intentional
Resolve which catalog is canonical (62-thread or 459-line) and document the choice

Acceptance

A fresh checkout with the README's uvicorn command produces a service where
/v1/threads/catalog returns threads and /v1/threads/resolve returns matches,
with no manual env-var editing

## README THREAD_PALETTE_PATH points to non-existent file **Repo:** Mark/easystitch-service **Severity:** Medium — service appears non-functional out of the box **Found:** 2026-09-08 full shakedown ### Symptom README §Configuration documents: > THREAD_PALETTE_PATH — Default: `/data/brother_pr10.json` But that file doesn't exist in this repo, the engine repo, or anywhere on the filesystem. Following the README literally produces a broken service: ``` GET /v1/threads/catalog -> {"catalog": []} POST /v1/threads/resolve -> {"error": "catalog_unavailable"} (HTTP 503) ``` The correct path is `/home/b/Projects/easystitch-service/data/brother_pr10.json` (62-thread, 3.5KB catalog that ships in this repo). ### Why there are two catalogs - `Mark/easystitch-service/data/brother_pr10.json` — 62 threads (the one the service uses) - `Mark/easystitch/src/embroidery_converter/thread_catalogs/brother_pr10_polyneon.json` — 459 lines, richer, but the service doesn't reference it It's unclear which is canonical for production. ### Fix 1. Update README to default `THREAD_PALETTE_PATH` to a real path the repo ships with 2. Or commit the catalog at `/data/brother_pr10.json` if the absolute path is intentional 3. Resolve which catalog is canonical (62-thread or 459-line) and document the choice ### Acceptance - A fresh checkout with the README's uvicorn command produces a service where `/v1/threads/catalog` returns threads and `/v1/threads/resolve` returns matches, with no manual env-var editing