-
Notifications
You must be signed in to change notification settings - Fork 109
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
Setting maxBytes = 0 does not work #41
Comments
This is a legit issue and I can repro. Will work on a fix. In the meantime, the workaround is to set the max bytes to be |
NSProgrammer
added a commit
that referenced
this issue
Feb 21, 2019
- Fix bugs related to capping the sizes of caches - Capping a cache to `0` bytes would not completely disable it as documented, fixed - Setting the max ratio value to a negative value would not use the default value as documented, fixed - Thanks to @jml5qh for filing this issue (#41) - Analyzer warning fixes too (not actual bugs)
Merged
NSProgrammer
added a commit
that referenced
this issue
Feb 21, 2019
- Fix bugs related to capping the sizes of caches - Capping a cache to `0` bytes would not completely disable it as documented, fixed - Setting the max ratio value to a negative value would not use the default value as documented, fixed - Thanks to @jml5qh for filing this issue (#41) - Analyzer warning fixes too (not actual bugs)
Resolved with merge #42 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In our project, we don't want a disk cache so we set [TIPGlobalConfiguration sharedInstance].maxBytesForAllDiskCaches = 0. However, that doesn't seem to be working. I DM'd with @NSProgrammer and he confirmed there are some places where 0 == off and others where 0 == unlimited (ex:
ios-twitter-image-pipeline/TwitterImagePipeline/TIPGlobalConfiguration.m
Line 542 in 8b3eff1
The text was updated successfully, but these errors were encountered: