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

On Windows, `report.test.ts`'s unwritable-folder case creates `\dev\null\nope` at the drive root instead of meeting an unwritable folder

Abierto Apto para principiantes
#301 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@TheSeydiCharyyev ya está trabajando en esto.

Desde el 29/10/2026.

  • #302 de @TheSeydiCharyyev — abierto

Evaluación

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

Línea de trabajo

Lee packages/jest/src/diagnostics/__tests__/report.test.ts en torno al caso “never throws when the directory cannot be written” y packages/jest/src/diagnostics/report.ts en torno a la llamada recursiva a fs.mkdir. El issue sugiere usar un archivo de la carpeta temporal de la prueba como projectRoot; ejecuta el caso específico de Vitest en Windows y confirma que sigue pasando sin crear nada en la raíz de la unidad.

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

Descripción

Describe the bug

never throws when the directory cannot be written hands the diagnostics appender projectRoot: '/dev/null/nope' (report.test.ts), a folder no write reaches on Linux and macOS, where /dev/null is a device. On Windows Node resolves it against the root of the drive the run is on, and the appender's fs.mkdir(dir, { recursive: true }) (report.ts) creates it. So the case passes without meeting an unwritable folder, and leaves \dev\null\nope\.harness\diagnostics\unwritable.jsonl behind, holding the marks a and b.

While that folder exists, Windows programs that open /dev/null as a path from that drive open the folder instead: Git for Windows' git diff --no-index /dev/null <file> fails with error: Could not access '/dev/null/<file>'.

A projectRoot below a regular file fails the same way on every platform (ENOTDIR), so a file the test writes in its temporary folder would keep the case's premise on Windows too.

System Info
System:
  OS: Windows 11 10.0.26300
Binaries:
  Node: 26.12.1
  pnpm: 10.6.1
React Native Harness Version

main at 26b67ea4

Reproduction

https://github.com/callstackincubator/react-native-harness/blob/26b67ea4342d316ce105ac801a4a7f20fa711833/packages/jest/src/diagnostics/__tests__/report.test.ts#L564-L575

Steps to reproduce
  1. On Windows, in a checkout of main: pnpm install, then pnpm vitest run packages/jest/src/diagnostics/__tests__/report.test.ts -t "never throws when the directory cannot be written".
  2. The case passes: Tests 1 passed | 26 skipped (27).
  3. dir /s /b \dev on the drive the run is on lists what it made. I ran it from a drive mapped with subst, X:, so the folder landed there:
X:\dev\null
X:\dev\null\nope
X:\dev\null\nope\.harness
X:\dev\null\nope\.harness\diagnostics
X:\dev\null\nope\.harness\diagnostics\unwritable.jsonl

unwritable.jsonl:

{"label":"a","startTime":1793230779050.4949,"duration":0,"status":"ok","kind":"mark"}
{"label":"b","startTime":1793230779052.054,"duration":0,"status":"ok","kind":"mark"}

Expected: the case meets a folder it cannot write, as on Linux and macOS, and leaves nothing outside its temporary folder.

Actual: the case passes after creating the folders above at the root of the drive the run is on, with the two marks in unwritable.jsonl.

Lenguaje dominante
TypeScript
Estrellas
335
Forks
23
Merge medio
1 d 8 h
PR fusionados (30 d)
54

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 callstackincubator/react-native-harness

Todos los issues de callstackincubator/react-native-harness

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.