-
Notifications
You must be signed in to change notification settings - Fork 557
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Caching issue? #1360
Comments
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still an issue. |
I think this has to do with the internal code of Heimdall. I see nothing in the Photoprism Heimdall-App that should make it act like this. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This is most likely not an issue with Photprism, but instead the internal code of Heimdall. The issue can happen on every enhanced app. |
I have two instances of Photoprism that I have added to Heimdall.
Quite often this shows the same statistics for both instances, I reload the page a few times and it finally gets right. Please see attached pictures.
Could this be due to some request being cached?
I have validated multiple times that Photoprism API returns the correct information.
In the image below you see the same statistics for both instances (which is wrong).
In this image the statistics shows up correctly,
The text was updated successfully, but these errors were encountered: