[bug] Windows: memory writes and statusline fail on a fresh install (POSIX-only path…

Abierto
#2,774 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 5 días

Nadie ha tomado este issue todavía.

  • #2802 de @isihussain — cerrado sin fusionar

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bun, typescript
Área
backend, devtools

Línea de trabajo

Start with TOOLS/lib/Boundary.ts, TOOLS/MemoryWriter.ts, STATUSLINE/Admission.ts, and STATUSLINE/State.ts; trace the seven Windows path and permission failures described in the issue. Run the listed memory health check and pipe session JSON into LIFEOS_StatusLine.sh on Windows to reproduce them. Done means the health check has no critical findings, ledger verification succeeds, and the statusline renders every row.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What happened

On Windows every memory write is refused and the statusline crashes on every render, because several tools assume POSIX paths and permission bits

Summary

Environment

  • LifeOS 8.761.0, Windows 11, Bun 1.4.4 (Windows x64)
  • Claude Code 2.1.303, hooks run through Git Bash
  • The user-data folder is a directory junction from the install tree into the config tree

Summary

On Windows, every memory write is refused and the statusline crashes on every render. Both come from code that assumes / separators, a / filesystem root, or POSIX permission bits. Seven defects, each hidden behind the previous one.

Memory (health check reports "Latest reviewer run is failed")

  1. TOOLS/lib/Boundary.ts, confinedPath: an absolute walk starts at sep, so the first component it stats is a backslash followed by the drive letter, which never exists (ENOENT). Every absolute path is refused, including the real file inside the user-data repo. Relative paths pass. Error: EWRITE_FAILED: memory write refused at the system/user boundary ... does not resolve inside the USER_DATA repo. Fix: start from parse(p).root and join with cur.endsWith(sep).

  2. TOOLS/lib/Boundary.ts, atomicWrite: invariant((fstatSync(fd).mode & 0o777) === mode) always fails, because Windows reports 0o666 whatever mode was requested.

  3. TOOLS/MemoryWriter.ts, snapshotBeforeWrite: absPath.split("/").pop() returns the whole Windows path, which trips the invariant snapshot target ... must sit directly in ... memory-snapshots.

  4. TOOLS/MemoryWriter.ts: the invariant snapshot dir ... is wider than 0700 fails for the same reason as (2).

  5. TOOLS/MemoryWriter.ts (4 sites): abs.replace(CLAUDE_ROOT + "/", "") leaves the full drive-letter path as the ledger row's file key. CortexLedger.ts verify then reports entries-drift on files the writer itself just wrote.

Statusline (prints nothing)

  1. STATUSLINE/Admission.ts (3 sites): startsWith(this.directory + "/render-") throws INVARIANT VIOLATION: render lock must be scoped to inflight. Fix: use sep.

  2. STATUSLINE/State.ts, expandRoot: converts a drive-letter install root to the MSYS form (slash, drive letter, slash). Bun on Windows cannot open that form, so every read under state.root returns null. Visible effect: blank STATE row and no doctor line. Fix: keep the native path when process.platform === "win32".

Smaller items found on the way

  • TOOLS/MergeSettings.ts with a relative --output settings.json fails with EEXIST: file already exists, mkdir '.'. An absolute output path works.
  • TOOLS/Inference.ts line 483: spawnSync("id", ["-un"]).stdout.trim() throws when the USER variable is unset and id is not on PATH (PowerShell).
  • TOOLS/ParkedReplay.ts replays only EDRIFT items, so writes parked with EWRITE_FAILED are never replayed after the cause is fixed.
  • The header's flag emoji draws as two letters, because Windows fonts have no flag glyphs.

Repro

  1. Fresh install on Windows 11; let one session end so the memory reviewer fires.
  2. Run bun LIFEOS/TOOLS/MemoryHealthCheck.ts: overall is critical.
  3. Pipe any session JSON into LIFEOS/LIFEOS_StatusLine.sh: invariant violation.

Verification of the fixes

  • confinedPath: 12 accept and refuse cases pass, including .. escapes through the junction and targets in the system tree.
  • After all seven: the health check has 0 critical findings, CortexLedger.ts verify is OK, a reviewer run wrote entries unaided, and the statusline renders every row.

The patches are small, about 25 changed lines in four files. Happy to open a PR.

Details

  • Kind: bug
  • LifeOS version: 8.761.0

Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.

Lenguaje dominante
TypeScript
Estrellas
19.9k
Forks
2.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de danielmiessler/LifeOS

Todos los issues de danielmiessler/LifeOS

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.