Comunidad Guías…

Ayuda y problemas de rag-foundry-universal

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#338 Uploaded Markdown / Docling section ingestion fails: run_with_sections iterates an IR ExtractionResult · 0 comentarios #337 CI-06: embedding inputs must represent all stored source (chunk/embedder contract + reuse invalidation) · 0 comentarios #335 Phase 6 CI-01: generation-bound graph export and validated cache · 0 comentarios #334 Docs maintenance: fix broken links, log.md gaps, stale current-release line, and index discoverability · 0 comentarios #323 E1: implement the preregistered named-symbol-first candidate (ordering-only; one authorized run) · 0 comentarios #314 Design: define source-span semantics for decorated definitions (span vs stored text) · 0 comentarios #313 Design: make extractor behavior part of the incremental-reuse identity (stale persisted nodes) · 0 comentarios #309 Record skipped directories and reasons per ingestion generation; expose via HTTP and ORIENT · 0 comentarios #308 Review name-based directory exclusions (build, dist, target, vendor): legitimate packages may be silently dropped · 0 comentarios #270 E1: diagnose why the unchanged control replay timed out downloading the full graph (no selection/chunking/delivery changes) · 9 comentarios #294 E1 goal: bring the code-evidence experiment to an evidence-backed decision (tracking) · 0 comentarios #241 Content-level ingestion opt-out: YAML front-matter directive to exclude a file from RAG entirely · 2 comentarios #291 Ingestion: exclude answer-bearing files from an evaluation corpus by path (Markdown and non-Markdown), recorded with the generation · 0 comentarios #180 Ingestion source-revision provenance: pinned Git ref + resolved SHA + config fingerprint · 2 comentarios #287 Re-ingestion died on a single 90 s vector-store batch timeout: investigate pgvector insert latency and add bounded retry · 0 comentarios #286 A failed or interrupted re-ingestion leaves a previously ready repository with no servable generation · 1 comentarios #285 Ingestion status hides the failure reason: return a sanitized error from GET /v1/ingest-repo/{id} and show it in the UI · 1 comentarios #282 Implement the ADR-055 node-text read endpoint in ingestion_service (POST /v1/graph/repos/{repo_id}/nodes/text) · 0 comentarios #275 E1: target-first selection — the target is discovered 6/6 but reaches final context only 3/6; attribute the loss by stage · 1 comentarios