-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
have timeout for cache #1531
Comments
A caching issue came up again on a twitter thread, this time regarding the jplhorizon module (where ephemeris got updated server side, yet the cached version got used in the query). I marked both cache related issues (#1511) as critical for the next release, and I feel this should be resolved sooner rather than later. |
We have yet another affected module. Much as I love caching, maybe we need to start defaulting it to 'off' to circumvent these issues? |
#1634 meant to address this, reopen if it's not the case. |
Would be nice to have a mechanism to invalidate the cache. E.g. when new data is added at the serverside users should be able to automatically get access to that. Whether to achieve that with a timeout (which wouldn't work well right around when the new data is added, and would ignore cache unnecessary when there is no data added for a long time) or my some other means is up for discussion.
The text was updated successfully, but these errors were encountered: