-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
[Epic][CI] Migrate linter to Ruff #47991
Labels
bug
Something that is supposed to be working; but isn't
ci-test
enhancement
Request for new feature and/or capability
Comments
MortalHappiness
added
bug
Something that is supposed to be working; but isn't
ci-test
labels
Oct 11, 2024
@MortalHappiness I'd like to help with this! |
MortalHappiness
changed the title
[CI] flake8 version is too old to be compatible with Python 3.12
[Epic][CI] Upgrade flake8 to version 7.1.1
Oct 15, 2024
8 tasks
This was referenced Oct 17, 2024
Closed
Closed
Closed
8 tasks
pcmoritz
pushed a commit
that referenced
this issue
Oct 23, 2024
<!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> See #47991 When running the following `flake8` command to check for errors: ``` flake8 --select E225 --extend-exclude python/ray/core/generated,python/ray/serve/generated/,python/ray/cloudpickle/,python/ray/_private/runtime_env/_clonevirtualenv.py,doc/external/,python/ray/dashboard/client/node_modules ``` the following error occurs : ![image](https://github.com/user-attachments/assets/e595a58e-677d-480f-9490-f52e62e4f0cf) ## Related issue number Closes #48059 <!-- For example: "Closes #1234" --> ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., `git commit -s`) in this PR. - [x] I've run `scripts/format.sh` to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] I've added any new APIs to the API Reference. For example, if I added a method in Tune, I've added it in `doc/source/tune/api/` under the corresponding `.rst` file. - [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/ - Testing Strategy - [ ] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: LeoLiao123 <[email protected]>
@MortalHappiness we should explore replacing flake8 with https://github.com/astral-sh/ruff if we want to do the upgrade. |
@jjyao Do you mean to replace flake8 completely with ruff? |
Yes. Reasoning is that |
Jay-ju
pushed a commit
to Jay-ju/ray
that referenced
this issue
Nov 5, 2024
…oject#48188) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> See ray-project#47991 When running the following `flake8` command to check for errors: ``` flake8 --select E225 --extend-exclude python/ray/core/generated,python/ray/serve/generated/,python/ray/cloudpickle/,python/ray/_private/runtime_env/_clonevirtualenv.py,doc/external/,python/ray/dashboard/client/node_modules ``` the following error occurs : ![image](https://github.com/user-attachments/assets/e595a58e-677d-480f-9490-f52e62e4f0cf) ## Related issue number Closes ray-project#48059 <!-- For example: "Closes ray-project#1234" --> ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., `git commit -s`) in this PR. - [x] I've run `scripts/format.sh` to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] I've added any new APIs to the API Reference. For example, if I added a method in Tune, I've added it in `doc/source/tune/api/` under the corresponding `.rst` file. - [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/ - Testing Strategy - [ ] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: LeoLiao123 <[email protected]>
JP-sDEV
pushed a commit
to JP-sDEV/ray
that referenced
this issue
Nov 14, 2024
…oject#48188) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> See ray-project#47991 When running the following `flake8` command to check for errors: ``` flake8 --select E225 --extend-exclude python/ray/core/generated,python/ray/serve/generated/,python/ray/cloudpickle/,python/ray/_private/runtime_env/_clonevirtualenv.py,doc/external/,python/ray/dashboard/client/node_modules ``` the following error occurs : ![image](https://github.com/user-attachments/assets/e595a58e-677d-480f-9490-f52e62e4f0cf) ## Related issue number Closes ray-project#48059 <!-- For example: "Closes ray-project#1234" --> ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., `git commit -s`) in this PR. - [x] I've run `scripts/format.sh` to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] I've added any new APIs to the API Reference. For example, if I added a method in Tune, I've added it in `doc/source/tune/api/` under the corresponding `.rst` file. - [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/ - Testing Strategy - [ ] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: LeoLiao123 <[email protected]>
mohitjain2504
pushed a commit
to mohitjain2504/ray
that referenced
this issue
Nov 15, 2024
…oject#48188) <!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? <!-- Please give a short summary of the change and the problem this solves. --> See ray-project#47991 When running the following `flake8` command to check for errors: ``` flake8 --select E225 --extend-exclude python/ray/core/generated,python/ray/serve/generated/,python/ray/cloudpickle/,python/ray/_private/runtime_env/_clonevirtualenv.py,doc/external/,python/ray/dashboard/client/node_modules ``` the following error occurs : ![image](https://github.com/user-attachments/assets/e595a58e-677d-480f-9490-f52e62e4f0cf) ## Related issue number Closes ray-project#48059 <!-- For example: "Closes ray-project#1234" --> ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., `git commit -s`) in this PR. - [x] I've run `scripts/format.sh` to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] I've added any new APIs to the API Reference. For example, if I added a method in Tune, I've added it in `doc/source/tune/api/` under the corresponding `.rst` file. - [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/ - Testing Strategy - [ ] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: LeoLiao123 <[email protected]> Signed-off-by: mohitjain2504 <[email protected]>
MortalHappiness
changed the title
[Epic][CI] Upgrade flake8 to version 7.1.1
[Epic][CI] Migrate linter to Ruff
Dec 25, 2024
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something that is supposed to be working; but isn't
ci-test
enhancement
Request for new feature and/or capability
What happened + What you expected to happen
While running the pre-commit hook of flake8, error occurs if Python version is 3.12. It's because the version of flake8 is too old.
We decided to fix this issue by migrating to
ruff
linter.Versions / Dependencies
Python 3.12
Reproduction script
If python version is 3.9 -> no error
If python version is 3.12 -> has error
Upgrade the following packages to the newest version solves this issue:
Issue Severity
Low: It annoys or frustrates me.
flake8
upgrade subtasks tracking:Thanks for @CheyuWu 's comment here #48022 (comment)
pycodestyle
pyflakes
flake8-bugbear
https://github.com/PyCQA/flake8-bugbear
flake8-comprehensions
https://github.com/adamchainz/flake8-comprehensions
CI changes
flake8
andisort
withruff
#48508black
withruff format
#49436Cleanup
The text was updated successfully, but these errors were encountered: