Fix(windows): Allow 'sqlmesh clean' to delete cache file paths that exceed 260 chars#5512
Merged
Fix(windows): Allow 'sqlmesh clean' to delete cache file paths that exceed 260 chars#5512
Conversation
erindru
force-pushed
the
erin/fix-clean-windows
branch
from
23eff11 to
cc49d33
Compare
erindru
changed the title
themisvaltinos
approved these changes
Oct 9, 2025
georgesittas
approved these changes
Oct 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, on Windows, running
sqlmesh cleancan return aFileNotFounderror if it tries to delete a file path that is > 260 chars.This PR addresses this particular case.
Note that SQLMesh behaves badly on Windows if the entire project is located at a base path that exceeds 260 characters, because all the model / seed loading code that assumes paths work starts to subtly break.
This PR does not address that, just the cache file paths that we create that the user has no control over.