Skip to content

Prepare for and hold a second pyright/Ruff correction day [21st May] #8553

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

Open
2 of 5 tasks
GRyall opened this issue Oct 23, 2024 · 5 comments
Open
2 of 5 tasks

Prepare for and hold a second pyright/Ruff correction day [21st May] #8553

GRyall opened this issue Oct 23, 2024 · 5 comments
Assignees

Comments

@GRyall
Copy link
Member

GRyall commented Oct 23, 2024

Issue Description

As a developer working on IBEX I want to continue 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. This will follow on and add to the work started in #8527.

Acceptance Criteria

What is the acceptance criteria of this ticket? What should the reviewer expect to be complete?

  • Identify a day that the majority of the group are free and available and book it in the calendars
  • Everyone who can spends as much time as they can on this day fixing these issues
  • Open tasks from previous pyright ticket are continued
  • The named person on this ticket provides a breakdown of the work needed (including carried over) to facilitate the team undertaking the task (this has to be done before the day is held). Prepare for and hold a pyright/Ruff correction day (suggested date 17th October 2024) #8527 can be used as a starting point. The breakdown should make it possible to see at a glance who is working on what and to track PRs and completion of work.
  • If required, a follow up ticket for remaining work is created

How to Review

Before making a PR...

  • Provide verbose instructions for the reviewer to test that your changes work and fix the issue
  • Describe if/how you have implemented testing for this issue
  • Provide screenshots of the feature to help the reviewer if relevant

planning 69:00 2024/10/31

Time in recording of planning meeting: 00h12m 2024/11/28
Discussed planning 05/02/2025 00:30:30

@LowriJenkins
Copy link
Contributor

Might be good to briefly discuss at planning whether this needs to be another whole day, or we whether what remains isn't large enough to justify a full tech-debt style day.

@Tom-Willemsen
Copy link
Contributor

Friday is more important for this sprint, defer this to maybe January

@LowriJenkins
Copy link
Contributor

ISISComputingGroup/IBEX-device-generator#4 Open PR from previous pyright day

@LowriJenkins LowriJenkins added the 13 label Feb 5, 2025
@KathrynBaker KathrynBaker moved this to Backlog in PI_2025_02 Feb 5, 2025
@jackbdoughty jackbdoughty self-assigned this Mar 31, 2025
@jackbdoughty jackbdoughty moved this from Backlog to In Progress in PI_2025_02 Mar 31, 2025
@jackbdoughty
Copy link
Contributor

jackbdoughty commented Apr 3, 2025

What still needs doing. I am suggesting we make genie_python our main focus for the day with the rest of the core python repos that need doing at the bottom to be carried over.

genie_python

  • block_names.py (Ruff: ❌, Pyright: ❌)

  • channel_access_exceptions.py (Ruff: ❌, Pyright: ❌)

  • genie.py (Ruff: ✅, Pyright: ❌)

    • Started @jackbdoughty
    • Ready for Review PR (effects other files)
    • Under Review
    • Done
  • genie_advanced.py (Ruff: ✅, Pyright: ❌)

  • genie_alerts.py (Ruff: ❌, Pyright: ❌)

  • genie_api_setup.py (Ruff: ✅, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_blockserver.py (Ruff: ❌, Pyright: ❌)

  • genie_cachannel_wrapper.py (Ruff: ✅, Pyright: ❌)

  • genie_change_cache.py (Ruff: ❌, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_dae.py (Ruff: ❌, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_epics_api.py (Ruff: ✅, Pyright: ❌)

  • genie_experimental_data.py (Ruff: ✅, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_logging.py (Ruff: ❌, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_plot.py (Ruff: ❌, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_pre_post_cmd_manager.py (Ruff: ❌, Pyright: ❌)

  • genie_script_checker.py (Ruff: ✅, Pyright: ❌)

  • genie_script_generator.py (Ruff: ✅, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_simulate.py (Ruff: ❌, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_simulate_impl.py (Ruff: ✅, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_startup.py (Ruff: ✅, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_toggle_settings.py (Ruff: ❌, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_waitfor.py (Ruff: ❌, Pyright: ❌)

    • Started
    • Ready for Review
    • Under Review
    • Done
  • genie_wait_for_move.py (Ruff: ❌, Pyright: ❌)

  • mysql_abstraction_layer.py (Ruff: ✅, Pyright: ❌)

  • scanning_instrument_pylint_plugin.py (Ruff: ✅, Pyright: ❌)

  • utilities.py (Ruff: ❌, Pyright: ❌)

  • matplotlib_backend\ibex_websocket_backend.py (Ruff: ❌, Pyright: ❌)

After this is done, the following core python repos need doing.

  • Block server
  • install scripts
  • system tests
  • top level epics scripts (e.g check_scripts, build_ioc_startups)

@jackbdoughty jackbdoughty moved this from In Progress to Impeded in PI_2025_02 Apr 4, 2025
@jackbdoughty jackbdoughty changed the title Prepare for and hold a second pyright/Ruff correction day Prepare for and hold a second pyright/Ruff correction day [24th April] Apr 4, 2025
@jackbdoughty jackbdoughty moved this from Impeded to In Progress in PI_2025_02 Apr 23, 2025
@jackbdoughty jackbdoughty moved this from In Progress to Impeded in PI_2025_02 Apr 24, 2025
@Tom-Willemsen
Copy link
Contributor

comment to make project board checks happier

@jackbdoughty jackbdoughty changed the title Prepare for and hold a second pyright/Ruff correction day [24th April] Prepare for and hold a second pyright/Ruff correction day [21st May] May 9, 2025
@jackbdoughty jackbdoughty moved this from Impeded to In Progress in PI_2025_02 May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

5 participants