Skip to content
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

Fixes for errors reported by mypy 1.11.0 #18608

Merged
merged 15 commits into from
Aug 2, 2024

Conversation

nsoranzo
Copy link
Member

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@nsoranzo
Copy link
Member Author

@jmchilton How would you like the errors in lib/galaxy/objectstore/__init__.py to be fixed? See https://github.com/galaxyproject/galaxy/actions/runs/10133978191/job/28019706741

@jmchilton
Copy link
Member

I would say we should just replace the very generic signatures with the specific ones and pray nothing breaks. Might hit some bugs in the mean time but long term that sounds better. I need to finish the dataset uuid stuff but if this is still red tomorrow - I could try to work through it.

@nsoranzo
Copy link
Member Author

Thanks @jmchilton , I followed your suggestion but please double check!
Any help appreciated, there are still more than 70 mypy errors to fix.

@nsoranzo nsoranzo force-pushed the mypy_1.11.0 branch 4 times, most recently from 3c7d4df to 849a091 Compare July 30, 2024 17:58
@jmchilton jmchilton force-pushed the mypy_1.11.0 branch 4 times, most recently from 75d097b to f821e3b Compare July 30, 2024 20:47
@nsoranzo nsoranzo force-pushed the mypy_1.11.0 branch 4 times, most recently from 7511e95 to 398c1c7 Compare August 1, 2024 00:11
@nsoranzo
Copy link
Member Author

nsoranzo commented Aug 1, 2024

@jmchilton Only 17 mypy issues left, and all other tests (except the unrelated integration test failures) are green.
Do you have time to fix the remaining ones? I need to finish other stuff before my holidays start, and these look a bit tricky for me.

@jmchilton
Copy link
Member

I think the fixes are higher priority than the mypy upgrade itself. Can I recommend we strip out the mypy upgrade and just PR the fixes so they don't stale. I'd be willing to take that task on while you're away - I am not ready to commit to finishing the upgrade though.

@nsoranzo nsoranzo marked this pull request as ready for review August 1, 2024 17:14
@github-actions github-actions bot added this to the 24.2 milestone Aug 1, 2024
@nsoranzo
Copy link
Member Author

nsoranzo commented Aug 1, 2024

Can I recommend we strip out the mypy upgrade and just PR the fixes so they don't stale.

Sounds good, this part should be ready for review/merge.

@jmchilton
Copy link
Member

Wow - that is a lot of scary changes. I think we have really good test coverage for the object store stuff and that is what I'm most worried about. We also have good test coverage of the toolbox and manager things I think. I'm most worried about the data provider stuff but I walked through closely and I think it should be all fine and I'm not certain any of it is used at this point anyway.

@nsoranzo
Copy link
Member Author

nsoranzo commented Aug 1, 2024

Integration test failures unrelated.

@nsoranzo nsoranzo merged commit 51b723b into galaxyproject:dev Aug 2, 2024
51 of 54 checks passed
@nsoranzo nsoranzo deleted the mypy_1.11.0 branch August 2, 2024 10:55
Copy link

github-actions bot commented Aug 2, 2024

This PR was merged without a "kind/" label, please correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants