0xMiden / 0xMiden/miden-vm

Windows checkout fails because generated snapshot paths exceed default path length

Abierto
#3,602 5 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Rust
Estrellas
772
Forks
352
Merge medio
1 d 12 h
PR fusionados (30 d)
93

Descripción

On Windows, a fresh clone of `0xMiden/miden-vm` can complete the fetch but fail during checkout because several snapshot filenames exceed the default Windows path limit.

Repro from `C:\Users\omer\Desktop\miden` on Windows/PowerShell:

```powershell
git clone https://github.com/0xMiden/miden-vm.git miden-vm-scan
```

The clone ends with:

```text
error: unable to create file processor/src/fast/tests/snapshots/miden_processor__fast__tests__all_ops__fast__tests__all_ops__test_basic_block__stack_inputs_01_vec_____operations_01_vec__Operation__Noop_Operation__Noop_Operation__Clk_Operation__M.snap: Filename too long
...
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
```

This looks separate from the earlier reserved-character Windows issue (#2561 / #2580): these paths do not rely on `::`; they are just too long for a default Windows checkout path.

Why this matters:
- Windows contributors cannot get to a clean working tree with the default clone command.
- The failure happens before any project-specific setup or tests can run.

A couple of possible fixes would be shortening the generated snapshot names or moving those snapshots under a shallower path. A short note in contributor docs about `core.longpaths` could help, but it would not fix the default clone experience.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.