-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add thumbnail.save configuration option. #660
Conversation
If this option is set to False, then do not save newly-generated thumbnails to the disk. Previously saved thumbnail images will be used normally and will never be deleted. This saves space and reduces drive writes at the cost of extra computational overhead by making the original image be reopened each time the thumbnail is loaded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a bunch, once again with tests and everything 😊
I added a few tiny nitpicks + questions, should be trivial to solve.
Looks like one of the tests timed out at |
Yes, unfortunately the runner is extremely slow from time to time (one can see that actually all tests progress a lot slower). I have absolutely no clue why, this only happens on CI, haven't had any issues locally. Noted a while ago in #335. EDIT: re-ran the workflow, works as expected, this is my go-to super annoying workaround until any idea why this happens ... |
Continuing #651 changes. Also, the
check_thumbails_created
intests/unit/utils/test_thumbnail_manager.py
might be a typo. Figured this should probably be another pull request or quick commit from maintainers, though.If this option is set to False, then do not save newly-generated thumbnails to the disk. Previously saved thumbnail images will be used normally and will never be deleted.
This saves space and reduces drive writes at the cost of extra computational overhead by making the original image be reopened each time the thumbnail is loaded.