Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

v2: sessions with path=NULL (around v1's add_session_path schema change) are missing from project session lists

Abierto Apto para principiantes
  • ¿Algo no está bien?
#51,144 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, database

Línea de trabajo

Empieza por packages/core/src/session/store.ts alrededor de la línea 108 y compara el filtro con ámbito de proyecto con packages/opencode/src/session/session.ts alrededor de las líneas 970-976. Comprueba cómo SessionStore.list gestiona una subruta raíz y reproduce la consulta sobre las filas en las que path IS NULL. Se considera terminado cuando las sesiones raíz correctamente atribuidas aparecen en la lista del proyecto sin cambiar el comportamiento de todos los proyectos.

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

Descripción

Description

Sessions with path = NULL are missing from project session lists after the v1→v2 upgrade, even though their project_id is correct.

v1 began with no path column; 20260428004200_add_session_path added it (default NULL), and v1's inserts still left it NULL for root-level sessions for a while (in our DB: a clean NULL window 2026-04-03→05-05, with every later session writing ''). The v1→v2 importer copies path verbatim, so these rows arrive in session_v2 with path IS NULL. The project-scoped picker sends {project, subpath: ''} and SessionStore.list filters with an exact eq(SessionTable.path, input.subpath) (packages/core/src/session/store.ts:108) — in SQL, NULL = '' is not true, so the rows are excluded. The projector only rewrites the path of the session that triggered a Resolved event; historical rows are never backfilled.

Scope in our DB (opencode 2.0.14, upgraded from 1.18.x): 90 sessions — 88 in one git repo (87 top-level, mostly user-initiated forks, ~1,300 messages total) + 2 in a second repo. All have directory = project.worktree, so the correct value is ''. They are only reachable via "all projects" scope / global search.

This is a different defect from #50980 (where the row is absent from session_v2 entirely) and from the project_id='global' family (#50551, #50800, #50999): here the project attribution is right, only path is null.

Plugins

None relevant (server-side data/filter behavior).

OpenCode version

2.0.14 (affected, by source comparison: 2.0.14–2.0.16; not fixed on latest tag)

Steps to reproduce
  1. In opencode v1, create sessions in a git repo root during the window where v1 didn't write path (around the 20260428004200_add_session_path change — e.g. after the path column exists but before v1 started writing '').
  2. Upgrade to v2.0.14–2.0.16 and open that repo. The import copies path = NULL into session_v2.
  3. List sessions in the project: the NULL-path sessions don't appear, though "all projects" scope shows them.

Check your own DB:

SELECT project_id, directory, COUNT(*) FROM session_v2 WHERE path IS NULL GROUP BY 1, 2;
Expected Behavior

Sessions whose directory equals the project worktree should be listed at subpath = '', i.e. NULL should be treated as the empty path (the dev branch already adds this: and(isNull(path), eq(directory, …)) at packages/opencode/src/session/session.ts:970-976).

Related issues
  • #35750 — v1-era: new path column not back-filled during migration (origin of these NULLs)
  • #50980 — sister symptom: v1-era session missing from session_v2 entirely
  • #50551 — the project_id='global' family (different root cause, same picker filter)
Operating System

Arch Linux, x86_64

Terminal

kitty

Lenguaje dominante
TypeScript
Estrellas
209k
Forks
27.5k
Merge medio
8 h 43 min
PR fusionados (30 d)
380

Preparar el entorno

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 anomalyco/opencode

Todos los issues de anomalyco/opencode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.