gauravworkss / yahoo-finance-managed

Automatically exported from code.google.com/p/yahoo-finance-managed
0 stars 0 forks source link

Invalid QuotesDownload LastTradePriceOnly values #20

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hello,
Recently the LastTradePriceOnly value retrieved via QuotesDownload is getting 
invalid values assigned during calls. Example, every 3rd or 5th call for a 
quote for symbol MSFT gets a value like 505545800.00. This happens with NYSE 
and Nasdaq quotes and only started occurring last week. I'm trying this via the 
.net libary and also tried the latest uploaded dlls.

What is the expected output? What do you see instead?
A valid quote for LastTradePriceOnly such as 27.05 instead of a value like 
505545800.00. This happens intermittently.

Original issue reported on code.google.com by apatel4...@gmail.com on 25 Jul 2011 at 6:05

GoogleCodeExporter commented 8 years ago
Hi,
I know that bug, but it's a Yahoo! bug. 
At first I also thought it's a failure of the library although I didn't change 
anything in quotes download and parsing process. I used a http sniffer and the 
urls are correct. Then I tried the same url (same id and properties) a couple 
of times direct in my browser and the result was the same. Irregularly I 
received some confusing results. Also not only the price value is fault. In 
same response the name of the ID was cutted.
So, when I didn't change anything in QuotesDownload and my browser also 
reproduces the problem, I deduce that it's a problem of Yahoo! server. I can't 
do anything in this case.

A workaround would be to proof if the LastTradePriceOnly value is over 500 
million or so and to decide that the result is invalid and to retry the 
download.
In my experience, if the result was invalid, the value was everytime over 500 
million.

best regards

Maas

Original comment by Maas...@gmail.com on 25 Jul 2011 at 7:05

GoogleCodeExporter commented 8 years ago
Hello, Thank you for your response and for looking into the issue.
I'll add code to validate the response as suggested to see if that will
work.

-Atul

Original comment by apatel4...@gmail.com on 26 Jul 2011 at 2:57