-
Notifications
You must be signed in to change notification settings - Fork 2
Prepare for and hold a pyright/Ruff correction day (suggested date 17th October 2024) #8527
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
Comments
To maximise the benefit of this day, I think we should focus on core/central pieces of code rather than beamline or device-specific stuff. Also try to target repos with higher churn as fixing issues in those repos will have biggest benefit. Initial repos to target (we likely won't get through all of these):
|
I suggest also checking that the device generator generates devices that are compliant (my device from the old generator is not, apologies if this has already been done) |
Some of the genie python files will be done by https://github.com/ISISComputingGroup/genie_python/pull/439/files as well |
Some changes in the Config Checker repository: PR |
Do we want to propose a follow up to this ticket to deal with the area's not dealt with during this one? i.e. Blockserver, system tests, reflectometry server, and top level epics scripts? |
Follow on ticket: #8553 |
Remaining PRs to complete reviews for before this issue can be closed: All others have been reviewed and merged. |
There are a number of repos which haven't been touched. Also for upgrade, when I created the PR, I wasn't aware that the ruleset I was using and the one builds are using aren't same. So I am doing more change to Upgrade (So the PR is really not ready). |
Yes - that is why there is a follow on ticket. I think this ticket can be considered complete when the work done for the day has been reviewed and merged.
Understood - my comment was a holding one so it is clear at a glance why the ticket is still in review, not a chase. |
The PR for the upgrade module is now available for review --> PR_UPGRADE |
Are the remaining PR's here still under review? or is this a case of people all thinking someone else is looking into this? |
The device generator one has outstanding comments. I briefly looked at the epics-upgrade one, but am not actively reviewing it. |
I'll have a look at the epics upgrade one then |
Just device generator left to do |
completion of ISISComputingGroup/IBEX-device-generator#4 has been moved into #8553. All other PRs have been reviewed, so closing this ticket. |
Uh oh!
There was an error while loading. Please reload this page.
As a developer working on IBEX I want to clear out and correct the legacy pyright/ruff errors that are in the system now that we have instigated these checks as standard so that small/urgent changes don't lead to lots of fixing.
Acceptance Criteria
Notes
The text was updated successfully, but these errors were encountered: