-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Tool Shed 2.0 fixes #16825
Tool Shed 2.0 fixes #16825
Conversation
Thanks for the fix - this is clearly a John problem and I will endeavor to find some time to fix up these tests. |
- test-install-client: 'standalone' | ||
python-version: '3.10' | ||
shed-api: 'v2' | ||
shed-browser: 'playwright' |
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.
I was "attempting" to only testing a subset of configurations because I thought all against all on the these combinations would be too much testing for such a niche feature. Does this configuration double the number of tool shed tests we're running?
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.
Yes, from 4 to 8. If you think that some of these combinations are not worth to be run on both Python versions, I can redo the matrix to run them only on Python 3.7.
dc01750
to
3d19b73
Compare
I initially messed up the second commit (fixed now), so the failing TS tests are actually much less. Edit: The errors are all due to the randomly occurring |
1dbf66f
to
d6104c6
Compare
d6104c6
to
807a487
Compare
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.
Looks good to me!
3c4f3a3
to
a56a475
Compare
This comment was marked as resolved.
This comment was marked as resolved.
374c45e
to
5caa90c
Compare
@jmchilton Not sure if on purpose, but diff --git a/mypy.ini b/mypy.ini
index fe479abe7d..f9212dbd4e 100644
--- a/mypy.ini
+++ b/mypy.ini
@@ -4,7 +4,11 @@ plugins = pydantic.mypy
show_error_codes = True
ignore_missing_imports = True
check_untyped_defs = True
-exclude = lib/galaxy/tools/bundled|test/functional|.*tool_shed/test/test_data/repos
+exclude = (?x)(
+ ^lib/galaxy/tools/bundled
+ | ^test/functional
+ | .*tool_shed/test/test_data/repos
+ )
pretty = True
no_implicit_reexport = True
no_implicit_optional = True I get more than 800 mypy errors, even after some fixes added here. Edit: To clarify, not planning to fix them all here, just a heads-up, will open a separate issue unless that was on purpose. |
Introduced in galaxyproject#16787 .
Broken in commit 3238b21 .
and the deleted field in the response. Rationale: it is not particularly useful, but both: GET /api/categories GET /api/categories/<encoded_id>/repositories work on TS 2.0, so it's weird that this one is missing. Also, it was breaking BioBlend's https://bioblend.readthedocs.io/en/latest/api_docs/toolshed/all.html#bioblend.toolshed.categories.ToolShedCategoryClient.show_category
Introduced in commit 1711e96 .
179e1f3
to
763e236
Compare
763e236
to
048d792
Compare
This is ready from my side, the failing TS tests are either:
|
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.
Awesome, thanks a lot @nsoranzo!
These are legacy repo contents used for testing that used be locked in tar balls. The repositories I think shouldn't be updated. This isn't code we're maintaining - it is test data that should remain unchanged so we know we're doing the same things. But maybe I've excluded too much? |
I'm going to go ahead and merge #16872 then - it looks good to me and it is needed for this. |
@jmchilton I think you've misread the diff in my comment above, |
yarn build
GET /api/categories/<encoded_id>
and thedeleted
field in the response.A bunch of ToolShed tests are failing, but they were simply not being run previously.
We can either merge this and fix the failing tests in separate PRs, or use this PR to push the fixes, but I don't have time to look into them currently.
How to test the changes?
(Select all options that apply)
License