-
Notifications
You must be signed in to change notification settings - Fork 73
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
Returning wrong historical data during runtime app #64
Comments
Hi @Thyen-Radek, |
Hi @lagerfeuer
So technically there i am getting 10 or 11 newest prices of BTC, at least i should right ? Same happens in jupyter notebook, whenever i run cell i won't get the newest historical prices but technically i am not sure how to explain but in above example i showed latest BTC price with using Well in the end i am pretty sure the |
Well i found the issue in library method:
So i need to pass to the function I am pretty sure it should be more clear in library or at least timeStamp should be always passed to achieve what we want.
in function:
|
@Thyen-Radek Thanks for the detailed explanation. You are indeed right, it's a bug. And you already outlined the solution. Feel free to open a PR, not sure when I'll get to it. |
I encountered recently issue with getting historical data during runtime app, for example Pyqt5 or even
running it on jupyter notebook. Here is example data:
Time now: 2023-06-13 12:07:23.156518
Time of data: 2023-06-13 02:09:00
The reason of that difference of time is because i ran kernel at night.
It always returns the data from the time kernel was started, so to get the real time data i would have to restart the kernel.
The same thing happens when using application in Pyqt5. However using
cryptocompare.get_price(...)
it always returns the newest value. Somewhere i read that it could be caching mechanism implemented in the library I am not sure if it was meant to be like this. Is there any solution to overcome this problem? Maybe it's only at my side and just can't address the issue.The text was updated successfully, but these errors were encountered: