-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cache uses filenames that might be too long on some systems #4172
Labels
T: bug
Something isn't working
Comments
Thanks for reporting. #4174 has a more detailed writeup. I think we should do a few things:
We can put out an extra release (24.1.1) once that's done. |
JelleZijlstra
added a commit
to JelleZijlstra/black
that referenced
this issue
Jan 26, 2024
- Ensure total file length stays under 96 - Hash the path only if it's too long - Proceed normally (with a warning) if the cache can't be read Fixes psf#4172
JelleZijlstra
added a commit
that referenced
this issue
Jan 26, 2024
- Ensure total file length stays under 96 - Hash the path only if it's too long - Proceed normally (with a warning) if the cache can't be read Fixes #4172
Fix is merged. I think I'll release 24.1.1 either later today or tomorrow, depending on we get other bug reports that we'd want to address. |
Fixed for me. thanks @JelleZijlstra and @hottwaj for reporting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Running black 24.1.0 (without --check) can produce filenames in user's cache folder that are too long for some filesystems e.g. eCryptFS only allows filenames that are 143 chars long
The resulting error is:
Environment
The text was updated successfully, but these errors were encountered: