Walkthrough

The PR consolidates development tooling by removing individual formatter and linter packages (black, isort, flake8) from the workers package dependencies and their corresponding configuration blocks, replacing them with comments indicating repo-wide formatting and import-sorting is now handled by ruff.

Changes

Development tooling consolidation

🎯 1 (Trivial) | ⏱️ ~2 minutes

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    subgraph Before["Before this PR (workers dev deps)"]
        B1[black] --> L[Lint / Format]
        B2[isort] --> L
        B3[flake8] --> L
        B4[ruff - repo root] --> L
    end

    subgraph After["After this PR (workers dev deps)"]
        A1[ruff - repo root only] --> L2[Lint / Format / Import Sort]
    end

    subgraph Kept["Still in workers dev deps"]
        K1[mypy] --> TC[Type Checking]
        K2[pytest / pytest-asyncio / pytest-mock / pytest-cov] --> T[Testing]
        K3[debugpy] --> D[Debugging]
    end

_{Reviews (2): Last reviewed commit: "Commit uv.lock changes" | Re-trigger Greptile}

Fixed. The root uv.lock regeneration came from a stray Commit uv.lock changes commit (135099d) that downgraded revision 3→1 and stripped upload-time metadata. I've dropped that commit via force-push — the branch now contains only the original 6a7b79310 commit touching workers/pyproject.toml + workers/uv.lock. Root uv.lock is back to its pre-PR state (revision = 3, untouched).

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Unstract test results

Per-group results

Critical paths

⚠️ Critical paths not yet covered

• auth-login — User can log in and obtain a session cookie. (entry: POST /api/v1/auth/login; declared coverage: no groups declared)
• adapter-register-llm — Register and validate an LLM adapter. (entry: POST /api/v1/adapter/; declared coverage: no groups declared)
• workflow-create-execute — Create a workflow, configure source+destination, execute, poll, fetch result. (entry: POST /api/v1/workflow/{id}/execute/; declared coverage: e2e-workflow)
• api-deployment-run — Deploy a workflow as an API, POST a document, receive structured JSON. (entry: POST /deployment/api/{org}/{name}/; declared coverage: e2e-api-deployment)
• prompt-studio-fetch-response — Prompt Studio: create project, add prompt, run single-pass, get response. (entry: POST /api/v1/prompt-studio/prompt-studio-tool/{id}/fetch_response/; declared coverage: e2e-prompt-studio)
• pipeline-etl-execute — Run an ETL pipeline from source connector to destination. (entry: POST /api/v1/pipeline/{id}/execute/; declared coverage: no groups declared)
• usage-token-tracking — Per-execution token usage is recorded and retrievable. (entry: GET /api/v1/usage/get_token_usage/; declared coverage: no groups declared)
• workflow-execution-fan-out — Multi-file workflow execution fans out to file-processing workers and rejoins. (entry: internal: backend → rabbitmq → workers/file_processing; declared coverage: no groups declared)
• callback-result-delivery — Async results are posted back via the callback worker. (entry: internal: workers/callback → backend /internal endpoints; declared coverage: no groups declared)