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
Many Vizier fixes #2012
Many Vizier fixes #2012
Conversation
WIP: need to fix tests. |
Codecov Report
@@ Coverage Diff @@
## master #2012 +/- ##
==========================================
+ Coverage 67.00% 67.02% +0.02%
==========================================
Files 411 411
Lines 27149 27164 +15
==========================================
+ Hits 18192 18208 +16
+ Misses 8957 8956 -1
Continue to review full report at Codecov.
|
I should probably have said so earlier: this PR is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we keep the test around and fix it so that it works with the current implementation? I prefer not to remove a test when we still support that functionality
@keflavich I will try to make it work. I also need to take care of a bug reported in #1962. |
@keflavich The test I had removed is back. I had to adjust post_mockreturn to handle the new VizieR list format. I also have a fix for the bug reported in #1962. |
…ll or equivalent is used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready to merge?
@keflavich, I have two failing remote tests. With the many changes I have in that PR, I am not too surprised. |
Ah, ok. Are you still working on it, then? |
I guess so: `Vizier.find_catalog()' is not happy. Let me send a note when all the tests pass. |
@keflavich Are the remote tests supposed to pass? |
Ideally yes! But if there are upstream changes that break tests, we may
just need to note that and move on.
|
When I run the code of |
It looks like I haven't changed anything related to |
OK. Could you open a new issue noting the specific remote failures, so we don't lose track of them? I'll merge this. Thanks. |
This would need a changelog (rule of thumb: if there is a user facing issue/API bug report, then we need the entry) |
This a re-implementation of Vizier.query_region() to support list of coordinates. The API on the Vizier side seems to have changed. This should fix #1962, fix #1826, fix #1502.