fix: FalkorDB result parsing, embeddings routing, triples query response, graph visualization

- Fix FalkorDB triples query: client v5 returns objects not arrays, use named field access
- Fix embeddings service: align spec names to "embeddings-request"/"embeddings-response"
- Fix client triplesQuery: read `triples` field instead of `response` from backend
- Fix graph page crash: guard against non-array triples, accept literals as entity nodes
- Add seed:demo script for AI industry knowledge graph (254 triples, 64 entities)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
elpresidank 2026-04-10 04:59:36 -05:00
parent 580ee319a3
commit f2b376abef
7 changed files with 837 additions and 31 deletions

View file

@ -18,11 +18,11 @@ export abstract class EmbeddingsService extends FlowProcessor {
this.registerSpecification(
new ConsumerSpec<EmbeddingsRequest>(
"request",
"embeddings-request",
this.onRequest.bind(this),
),
);
this.registerSpecification(new ProducerSpec<EmbeddingsResponse>("response"));
this.registerSpecification(new ProducerSpec<EmbeddingsResponse>("embeddings-response"));
this.registerSpecification(new ParameterSpec("model"));
}
@ -34,7 +34,7 @@ export abstract class EmbeddingsService extends FlowProcessor {
const requestId = properties.id;
if (!requestId) return;
const responseProducer = flowCtx.flow.producer<EmbeddingsResponse>("response");
const responseProducer = flowCtx.flow.producer<EmbeddingsResponse>("embeddings-response");
try {
const vectors = await this.onEmbeddings(msg.text, msg.model);