Ctrl K
ComunidadGuías…

Ayuda y problemas de HARTOS

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

#117 Discard the 3 landed PR branches and re-cut from main (parallel-path-fixes must not be rebased forward) · 4 comentarios#105 Design review: tell us what you would have built differently · 0 comentarios#104 Verify: do three nodes beat one? The convergence threshold (VERIFICATION.md row 16) · 0 comentarios#103 Verify: does intelligence compound across nodes? (VERIFICATION.md rows 14-15) · 0 comentarios#102 Verify: run HART OS against a Reachy Mini (VERIFICATION.md rows 13-14) · 0 comentarios#95 Verify: does the Pi 4 image boot? (VERIFICATION.md row 1) · 0 comentarios#96 Verify: does GPIO actually toggle from the agent? (VERIFICATION.md row 2) · 0 comentarios#97 Verify: what tokens/sec does the CPU-only path manage on a Pi? (VERIFICATION.md row 3) · 0 comentarios#98 Verify: does a 4GB board degrade honestly? (VERIFICATION.md row 4) · 0 comentarios#99 Verify: can the Claude Code co-pilot daemon complete one loop on a node? (VERIFICATION.md row 10) · 0 comentarios#100 Verify: can two machines borrow compute from each other? (VERIFICATION.md row 7) · 0 comentarios#101 Verify: does a borrow settle what it owes? (VERIFICATION.md row 8) · 0 comentarios#94 Two deploy workflows fight over the same Docker tag if DEPLOY_ENABLED is ever turned on · 0 comentarios#93 The 19 nixosTest VM checks have never passed in CI, and nothing triggers them · 0 comentarios