chore:remove flake8

[tchow-zlai]

Summary

Ruff was introduced recently, removing flake8 checks since it's uncessary now

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

Summary by CodeRabbit

• Chores
  • Removed an outdated code style check from the Python testing workflow.
  • Updated configuration settings to streamline internal testing processes.

[coderabbitai]

Walkthrough

The pull request removes the flake8 linting step from the GitHub Actions Python workflow and deletes the corresponding flake8 configuration from the tox.ini file. The workflow will now only perform linting with ruff and run tests, while any style enforcement provided by flake8 is no longer applied.

Changes

File(s)	Change Summary
.github/workflows/test_python.yaml	Removed the step that activated a Python environment and ran flake8 linting.
api/python/tox.ini	Deleted the [flake8] section and the max-line-length = 120 parameter.

Sequence Diagram(s)

sequenceDiagram
    participant CI as GitHub Actions
    participant Env as Python Environment
    participant Linter as Ruff Linter
    participant Tester as Test Runner

    CI->>Env: Set up Python environment
    CI->>Linter: Run linting with ruff
    CI->>Tester: Execute tests

Loading

Possibly related PRs

• fix: minor adjustment #486: Involves removal of flake8 settings from the project.
• chore: update devnotes #97: Related to eliminating the flake8 configuration section from project files.
• feat: refactor github workflows to do conditional CI/CD #98: Connects to changes in the GitHub Actions workflow regarding flake8 linting.

Suggested reviewers

• piyush-zlai
• nikhil-zlai
• chewy-zlai

Poem

In the realm of code so wide,
Flake8 steps have bid goodbye,
Ruff now reigns in linting's stead,
Tests march on with strength ahead,
Cheers to change, let bugs subside!
🚀✨

Warning

Review ran into problems

🔥 Problems

GitHub Actions and Pipeline Checks: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 0ee9fc1 and 294aba0.

📒 Files selected for processing (2)

• .github/workflows/test_python.yaml (0 hunks)
• api/python/tox.ini (0 hunks)

💤 Files with no reviewable changes (2)

• api/python/tox.ini
• .github/workflows/test_python.yaml

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: non_spark_tests
• GitHub Check: enforce_triggered_workflows

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.