Skip to content

fix(mcp): black formatting violation in mcp_bridge.py blocks CI #833

Description

@itomek

Summary

src/gaia/mcp/mcp_bridge.py:631 has a long dict literal on a single line that black wants to split across 4 lines. The file is in the repo's black-check scope (util/lint.py step 1/9), so every PR currently fails the Run Code Quality Checks CI job until this is fixed on main.

Surfaced while preparing release PR #831 (v0.17.3) — that PR doesn't touch mcp_bridge.py but inherits the failing check from main.

Reproduction

uv pip install black --quiet
uv run python -m black --check src/gaia/mcp/mcp_bridge.py
# → would reformat src/gaia/mcp/mcp_bridge.py
# → exit 1

Full diff:

--- src/gaia/mcp/mcp_bridge.py  (before)
+++ src/gaia/mcp/mcp_bridge.py  (after black)
@@ -626,11 +626,14 @@
         if not isinstance(data, dict):
             self.send_json(
                 400,
                 {
                     "jsonrpc": "2.0",
-                    "error": {"code": -32600, "message": "Invalid Request: expected JSON object"},
+                    "error": {
+                        "code": -32600,
+                        "message": "Invalid Request: expected JSON object",
+                    },
                     "id": None,
                 },
             )
             return

Origin

Introduced by #803 (fix(mcp): guard JSON-RPC handler against non-dict body). CI presumably passed at merge time with an older black version; the current pinned version flags it.

Fix

One command:

uv run python -m black src/gaia/mcp/mcp_bridge.py

Commit as style(mcp): apply black formatting to mcp_bridge.py. No behavior change.

Impact

  • Blocks all PRs on the Run Code Quality Checks status, including release PR Release v0.17.3 #831.
  • Low-risk fix; no production code behavior change.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdomain:platformFoundation: Lemonade, providers, runtime, install, packagingtrack:platformFoundation that both consumer-app and oem-pc tracks consume

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions