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
The new Web-Service is very unreliable #103
Comments
@novak-services We will check will resolve the issue ASAP |
Has there been any progress on this? The exact same issues still persist. |
same "Currency Rates Source Not Ready" for version 1.8 |
@qmhedging @BerendMosch @novak-services it is stable now. please check. |
I will implement if you find any better service to be used. |
Is the website down again? Because i am getting the currencyRatesNot available error on 1.8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am working in a project which uses forex-python regularly. But lately the webservice changed. We updated to 1.6. Since than, we got many troubles.
At first we got the error
So I incoporated the change, that was in one commit after the 1.6 release to prevent this error.
But after that, I still got some errors like that:
We always access past rates with a date.
I was curious, what the reason was, so I tried to access the API myself. I got some very strange results. Everything seems to be Ok, with latest rates and also at business days. But when I try a non-Business date, it really gets strange.
Here some examples, I got:
4.4.:
Particularly be aware here, that the base should be GBP, but is not!
5.4.:
Why do we get here USD? I tried the same call again, and was totally astonished.
5.4 Second Try:
So the results are not even stable and I am not sure, if errors due to this unstable results can not lead to wrong rate results, since rates are exchanged and also dates can be wrong (and even more?).
I even tried to use the API without base and symbols, but even than I got wrong results eventually.
So in my opinion this web service is not usable at all in this state. Even when it would not be unstable, on non-working days, this service can not provide results. Working around this would be very cumbersome. But with the instability, even a workaround would be error-prone.
My question here: Why do you use particularly this service and would it be feasible to use a different one?
The text was updated successfully, but these errors were encountered: