You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, some filesystems have quite short name restrictions. e.g. we had a bug report where this failed because the cache was on an encrypted filesystem where the max filename length is 144 characters (rather than the usual ext4 limit of 255).
Would it make sense to hash the (long) prefix as well as the contents?
The text was updated successfully, but these errors were encountered:
I'd be open to moving a bunch of that stuff from the directory name to the cache key. Perhaps it would make sense to retain pdict-v4-loopy-buffer_array-3.10? Want to cook up a PR?
Since #710 (perhaps),
memoize_on_disk
produces quite long filenames, for example:Unfortunately, some filesystems have quite short name restrictions. e.g. we had a bug report where this failed because the cache was on an encrypted filesystem where the max filename length is 144 characters (rather than the usual ext4 limit of 255).
Would it make sense to hash the (long) prefix as well as the contents?
The text was updated successfully, but these errors were encountered: