EKOSdocs
Docs / Reference Operate

Error Codes

Diagnostic codes emitted by the compiler passes.

Diagnostics are warnings written to the console summary and to .ekos/diagnostics/*.log. They do not stop the pipeline unless noted.

Code Emitted by Meaning What to do
SQL001 SQL analyzer no tables found in <file> — often a dialect parse failure Check [recover.sql] dialect rules
SQL002 SQL analyzer LLM enrichment output could not be parsed Structural analysis still applied; retry or raise [llm] max-tokens
SQL003 SQL analyzer LLM call failed (structural analysis still applied) Check provider, key, network
SQL004 SQL analyzer LLM named only some of a file's tables Raise [llm] max-tokens
GIT001 Git analyzer commit artifact not found in the store Re-run ekos build; check paths = ["."]
GIT002 Git analyzer failed to read a commit artifact ekos clean, rebuild
JS001 JavaScript analyzer cannot read an artifact Re-run ekos build
JS002 JavaScript analyzer malformed payload Rebuild; report if it persists
JS003 JavaScript analyzer unrecoverable syntax error in a source file Fix or exclude the file
SEM000 semantic compiler skipping an unreadable artifact, or no knowledge artifacts found Run ekos recover first
SEM001 semantic compiler an identity conflict Review; resolve --force to continue
SEM002 semantic compiler a warning while writing the CKM Check disk space and permissions
SEM003 semantic compiler fuzzy same-source merge candidates sent to review as unconfirmed SameAs Review with ekos_identity_review

Other messages worth knowing

Message Meaning
N identity conflict(s) detected — resolve manually … or pass --force ekos resolve failed on conflicts
search index schema is stale … open writable A read-only open of a ledger whose index predates a schema change; run ekos ledger repair
cannot open fact ledger at … Wrong --workspace, or no .ekos/ledger yet
skipping pass (cached) Informational: a pass reused cached output
N are expected File-object references (compile) Not an error: File objects resolve after ekos commit