vite: Windows: Can't pull changes because of "long file name" test file

Describe the bug

I am trying to pull the latest changes to my local fork (so I can submit a PR). I expect git to be able to pull these changes. On Windows, the following error appears.

vite-filename-test-issue

It appears that the test for long file name is indeed trying to create a filename that is too long. My local fork is 42 commits behind. The dialog above looks like it has hash references in git “tree-ish”.

Reproduction

Not possible because of issue

Steps to reproduce

Run a normal git pull on a windows machine.

System Info

Windows 10, git, github desktop, all at latest versions and patches.


  System:
    OS: Windows 10 10.0.19045
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900K
    Memory: 54.82 GB / 63.78 GB
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.8.0 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Spartan (44.19041.3570.0), Chromium (117.0.2045.60)


### Used Package Manager

npm

### Logs

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to [vuejs/core](https://github.com/vuejs/core) instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

About this issue

  • Original URL
  • State: closed
  • Created 9 months ago
  • Comments: 21 (21 by maintainers)

Most upvoted comments

Thanks for re-testing @epreston. Let’s close the issue then. Please get back to us if there are other problems related to this in the future.

@patak-dev I repeated the tests. It’s working. Sorry about pointing to older tests.

I am able to sync new and old local forks of vite now. Paths greater than 27 characters work. I have not made any modifications to the “global” git config or registry. Using a freshly rebuilt Windows 10 test machine.

The following path is working as before:

C:\Users\username\Documents\GitHub\vuejs\vite

Shorter paths are working:

C:\Repos\vite