-
Notifications
You must be signed in to change notification settings - Fork 6
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
Decrease requests to Open Exchange Rates #6
Comments
@AlexWayfer Thanks for the bug report. I'll look into it. |
@AlexWayfer Checking mtime isn't as simple as it sounds because the gem may not be configured to cache the results in a file. A better solution may be to record when the data was last fetched from the API rather than relying on the timestamp within the data. I'll think about it and patch it soon. |
OK, I got it. I think, you're right. |
I updated this and release 0.4.0 which fixes the issue. |
Thank you. |
We have a high load at weekends:
I think value of
data['timestamp']
is not updating at weekends and we try to update the whole data again and again… until there is Monday with the newtimestamp
.Probably, gem should check
File.mtime
forstale?
method.The text was updated successfully, but these errors were encountered: