Hili ni toleo la zamani. Toleo la sasa ni 0.4.1. daimon 0.4.1 · Lilitolewa:
Faili za kisakinishi 0.3.1
| Usanifu | Aina | Upeo | Ukubwa wa faili | Pakua | SHA256 |
|---|---|---|---|---|---|
| 64-bit | ZIP → Portable | — | — | github.com | VirusTotal |
Kiungo na SHA256 vinatoka kwenye manifest ya jumuiya ya Windows Package Manager. Linganisha hashi ya faili uliyopakua kabla ya kuiendesha.
Maelezo ya toleo
Bug Fixes
Qdrant: fix "unknown component type" on startup with existing collection
daimon serve was reporting unknown component type "qdrant" even when the Qdrant server was running and the collection was fully populated.
Root cause: ensureCollection always issued a PUT /collections/{name} request. Qdrant returns 400 when the collection already exists, which caused New() to return an error. sidecar.go silently discarded the error and fell through to the LLM registry, which produced the misleading "unknown type" message.
Fix: ensureCollection now GETs the collection first. If it exists (200), it returns immediately. If it doesn't exist (404), it creates it with PUT. Any other status is a real error.
Improved error reporting in sidecar wiring
Added HasVectorStore and HasGraphStore to the memory registry. sidecar.go now distinguishes between "type not registered" (try the next registry) and "type registered but factory failed" (fatal error with a clear message). Previously, a factory error from a known component type would silently fall through and produce a confusing "unknown type" error at the LLM registry.