TypeScript extraction rejects LLM replies that Python accepts
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 68/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- python, typescript
Direzione di ricerca
Read typescript/src/extraction/extractor.ts alongside src/selfgraph/extraction/extractor.py, focusing on the output models named in the issue and the strength validators. Compare the defaults and accepted values across the four extraction passes, then run the reproduction against embedded Kuzu. Done when the TypeScript insert accepts the omitted fields and strength cases described and behaves consistently with Python.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happens
The TypeScript extractor's output schemas mark optional fields as .nullable(), so the key must be present. Python's models give the same fields defaults. A reply that leaves out aliases, event_time, about_name, strength, actor_name, summary, rationale, outcome_name, alternative_names, status, or steps is accepted in Python and fails the whole insert.text in TypeScript with invalid_llm_output. stance defaults to preference in Python and is required in TypeScript.
Number handling for strength differs too. Python's _PrefOut.strength is a lax float: true and false are stored as 1.0 and 0.0, although insert.facts rejects a boolean strength (StrictFloat). NaN and infinity reach _validate_strength and are dropped per item. TypeScript rejects all of these at the output schema, failing the insert.
Providers in JSON or tool mode often omit null fields, so the same client works with one SDK and not the other.
Reproduce
On main (5a277c9), embedded Kuzu:
import { mkdtempSync } from "node:fs";
import { tmpdir } from "node:os";
import { join } from "node:path";
import { KuzuStore, SelfGraph } from "@hydradb/selfgraph";
async function run(name: string, replies: Record<string, unknown[]>) {
const llm = {
async generate({ output }: { output: { shape: Record<string, unknown> } }) {
const kind = Object.keys(output.shape)[0]!;
return { [kind]: replies[kind] ?? [] };
},
};
const g = new SelfGraph(new KuzuStore(join(mkdtempSync(join(tmpdir(), "sg-")), "g.kuzu")), { llm });
try {
const r = await g.insert.text("Ann works at Acme.");
console.log(name, "ok", r.entities.map((e) => e.id));
} catch (e) {
console.log(name, (e as { code?: string }).code, (e as Error).message);
} finally {
await g.close();
}
}
await run("missing aliases", {
entities: [{ type: "Person", name: "Ann" }, { type: "Company", name: "Acme" }],
relations: [{ from_name: "Ann", type: "WORKS_AT", to_name: "Acme", event_time: null }],
});
await run("missing stance", {
preferences: [{ subject_name: "Ann", key: "food", value_name: "Pizza", about_name: null, strength: null }],
});
await run("boolean strength", {
preferences: [{ subject_name: "Ann", stance: "preference", key: "food", value_name: "Pizza", about_name: null, strength: true }],
});
missing aliases invalid_llm_output LLM client returned an invalid result for the entities pass: entities[0].aliases: field required
missing stance invalid_llm_output LLM client returned an invalid result for the preferences pass: preferences[0].stance: expected 'preference' or 'disinterest'
boolean strength invalid_llm_output LLM client returned an invalid result for the preferences pass: preferences[0].strength: expected number
Python inserts all three: person:ann and company:acme with the relation, a preference with stance preference, and a preference with strength 1.0.
Cause
EntitiesOut, RelationsOut, PreferencesOut, and DecisionsOut in typescript/src/extraction/extractor.ts versus _EntityOut, _RelOut, _PrefOut, and _DecOut in src/selfgraph/extraction/extractor.py. The two need the same optional fields and defaults, and strength the same strictness in both.
- Lingua principale
- TypeScript
- Stelle
- 173
- Fork
- 58
- Merge medio
- 6h
- PR unite (30g)
- 120
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di hydra-db/selfgraph
-
approved-for-pr area: cli-mcp area: errors bug effort: S P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
hydra-db/selfgraph#401 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
approved-for-pr area: errors area: store bug effort: S P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
hydra-db/selfgraph#398 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
approved-for-pr area: errors area: write bug effort: S P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
hydra-db/selfgraph#392 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
approved-for-pr area: parity area: write bug effort: S P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
hydra-db/selfgraph#391 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di hydra-db/selfgraph
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
code-yeongyu/senpi#7139 ·
I maintainer di solito rispondono entro 1 giorno
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 1-3 ore Idoneità per principianti 72/100
lingdojo/kana-dojo#34395 · 1 commento · 5 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
bug status: needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
mastra-ai/mastra#31093 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
area:web p2 product:business triage:active type:bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 89/100
cuadrao-ai/argus#2328 ·
I maintainer di solito rispondono entro 1 giorno
-
bug frontend good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
nikhilb2/simple_invoicing#907 ·