joblib crashes when function name to cache is too long
See original GitHub issueI am using joblib to cache the results of a function and joblib crashes with the following error message:
OSError: [Errno 36] File name too long: '.joblib/joblib/__main__--home-nelle-Projects-EPICON-epiconWorkRepos-integration-scripts-mediation_bootstrapped_nnls-test_model_mrna_TFs_mirna_meth_bootstrapped_nnls'
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Joblib crashes after 2x n_jobs - Stack Overflow
The interesting part is it always crashes after calling pullSummaryData exactly 2* n_jobs . If n_jobs=3 , pullSummaryData will be called 6 times ......
Read more >joblib Documentation - Read the Docs
Using joblib's caching mechanism avoids hand-written persistence and implicitly links the file on disk to the execution context of the original ...
Read more >Development — joblib 1.3.0.dev0 documentation
Memory to properly handle caching for functions defined interactively in a ... Windows and large leaked files in /dev/shm under Linux in case...
Read more >Ray Core API — Ray 2.2.0 - the Ray documentation
For testing purposes ONLY. _tracing_startup_hook – If provided, turns on and sets up tracing for Ray. Must be the name of a function...
Read more >METADATA · aaronreidsmith/joblib - Gemfury
Metadata-Version: 2.1 Name: joblib Version: 0.14.1 Summary: Lightweight pipelining: ... In particular: 1. transparent disk-caching of functions and lazy ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I am having this issue on Windows 10, but it does not throw an error. The cache is not used, but does not let the user know that the caching has failed.
At minimum, it would be beneficial if the user was warned that the cache directory path name is too long.
Apparently this is important for jupyter notebooks where the whole path to the notebook ends up in the cache file name. With scripts it is not so bad because it is usually shorter i.e.
lib.module.file