-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Cache issues with JPLhorizons #2237
Comments
I have had the same issue. Did you find the way to fix this? @Mdevogele |
I did not fix it inside astroquery itself, but I got around it by using a try and except
|
cc @mkelley, though this is not a unique issue to jplhorizons and @keflavich added a fix for the same issue for simbad in #2187, something similar should do the trick here. |
Fix for issue #2237: do not cache results that cannot be parsed.
Hi,
I encountered this issue with JPLHorizons, but it might be present for other services.
For a brief moment, the Horizons API was returning errors to my queries.
Those queries have been stored in the cache although astroquery was recognizing them as faulty queries.
It resulted that when the issue was fixed on the Horizons side, my astroquery queries were still returning the same error as it was using the cache and was not trying to query Horizons again.
I thus had to add a try and catch to all my programs to avoid this issue and using a cache=False when the regular call with the cache fails while this could be built in the JPLHorizons module to not store the cache when the query fails
For the example, here was the error that the JPLHorizons was returning to me was:
ValueError: Query failed without known error message; received the following response:
BATVAR: no TLIST values found (or missing quotes)
WLDINI: error loading execution-control file.
Thanks!
The text was updated successfully, but these errors were encountered: