-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Fix issue 1332 (photos from external folders not shown) #1371
Fix issue 1332 (photos from external folders not shown) #1371
Conversation
762ea61
to
a2bab8e
Compare
2cfffa3
to
2dcfb7e
Compare
99ea945
to
8c34ea8
Compare
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.
@umgfoin thanks for your contribution. Unfortunately my dev setup is currently not running. Did you notice any performance Impacts with this change?
Do you think we should create an option to enable and disable external storages? Or can this be done via .nomedia files anyway? What do you think?
For me not noticeable: Loadtime for ~8K photos with empty photoCache till initial display: 15s
The |
@come-nc & @tacruc
This would NOT treat clearing an empty cache as an error, but still give a visual GUI-feedback, if something abnormal happened. |
8258635
to
a2e54d7
Compare
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.
@umgfoin Let's go.
Remove FileCache-usage in GeophotoService::getAll and GeophotoService::getNonLocalized Signed-off-by: umgfoin <umgfoin@users.noreply.github.com>
Signed-off-by: umgfoin <umgfoin@users.noreply.github.com>
Signed-off-by: umgfoin <umgfoin@users.noreply.github.com>
Signed-off-by: umgfoin <umgfoin@users.noreply.github.com>
a2e54d7
to
90689cc
Compare
GeophotoService::getAll tries to load filecache-entries by id for each photo-entity in the photomapper.
Since NC30 this regularly fails for images located on ext. storage: As a result, the corresponding photos won't get included in the distributed photosCache and thus don't show up on the map.
I yet don't see the root-cause for the cache-failures here, but imho, access to the filecache is not needed - neither does it provide any performance gain. I decided to remove the corresponding filecache-code and retrieve the required attributes (Etag and mimetype) from the anyway fetched file-object.
This fixes #1332
Other changes:
- A false failure-message when clearing the photo-cache was fixed.