davinci-resolve-mcp 4.13.2 → 4.13.4

package/CHANGELOG.md

@@ -2,6 +2,43 @@
 
 Release history for the DaVinci Resolve MCP Server. The latest release is summarized in the root README; older entries live here to keep the README focused.
 
+## What's New in v4.13.4 — Windows: the bridge claims its port exclusively
+
+Lands #292 from @AllastorV, case 2 of the Windows failures tracked in #278.
+
+### Fixed
+
+- **In-Resolve bridge (`src/utils/resolve_bridge.py`)**: on Windows
+  `SO_REUSEADDR` means "share a live port", not "rebind past `TIME_WAIT`", so a
+  new bridge bound on top of a stale one, the orphan check never raised
+  `BridgeConfigError`, and which bridge answered was undefined. On Windows the
+  listener now sets `SO_EXCLUSIVEADDRUSE` and leaves `allow_reuse_address` off,
+  so a second bind fails and the existing orphan message explains it. POSIX is
+  unchanged. Stopping and immediately restarting on the same port still works on
+  Windows (checked after 1 and 20 requests, with 20 `TIME_WAIT` rows).
+- **Windows users of the free-edition bridge:** the installer copies
+  `resolve_bridge.py` into Resolve's scripts folder, so re-run
+  `python scripts/install_resolve_bridge.py` to pick up this fix.
+
+## What's New in v4.13.3 — No bridge running is reported as unavailable, not as a modal dialog
+
+Lands #291 from @AllastorV, case 3 of the Windows failures tracked in #278.
+
+### Fixed
+
+- **Bridge client (`src/utils/resolve_bridge_client.py`)**: a timeout while
+  connecting to the in-Resolve bridge now raises `BridgeUnavailable` ("Start it
+  from Workspace > Scripts > resolve_bridge") instead of `bridge_timeout`
+  ("check for an open modal dialog"). On Windows a refused loopback connect
+  retries the SYN for about 2 s (measured 2.04 s), so with the 1 s timeout a
+  user with no bridge running was sent looking for a dialog. The kernel
+  completes the TCP handshake even while a modal dialog blocks Resolve, so a
+  connect that times out never means a dialog. A timeout after the connection
+  is up is still `bridge_timeout`. One timeout value, no new setting.
+- Two tests patch `socket.create_connection`, so Linux and macOS CI exercise the
+  Windows timing: a connect timeout is `BridgeUnavailable`, a read timeout is
+  still `bridge_timeout`.
+
 ## What's New in v4.13.2 — Three more Windows test failures fixed
 
 Lands #289 from @AllastorV, who re-ran the offline suite on v4.13.1 on Windows

package/README.md

@@ -2,7 +2,7 @@
 
 English | [简体中文](README.zh-CN.md)
 
-[![Version](https://img.shields.io/badge/version-4.13.2-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-4.13.4-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
 [![Tools](https://img.shields.io/badge/MCP%20Tools-37%20(390%20full)-blue.svg)](#server-modes)

package/README.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](README.md) | 简体中文
 
-[![Version](https://img.shields.io/badge/version-4.13.2-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-4.13.4-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
 [![Tools](https://img.shields.io/badge/MCP%20Tools-37%20(390%20full)-blue.svg)](#服务器模式)
@@ -12,7 +12,7 @@
 [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-> 本翻译对应 v4.13.2 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
+> 本翻译对应 v4.13.4 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
 
 一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
 

package/install.py

@@ -37,7 +37,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "4.13.2"
+VERSION = "4.13.4"
 # Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
 # Resolve's scripting bridge loads into newer interpreters on recent builds
 # (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "davinci-resolve-mcp",
-  "version": "4.13.2",
+  "version": "4.13.4",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/src/granular/common.py

@@ -91,7 +91,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "4.13.2"
+VERSION = "4.13.4"
 logger = logging.getLogger("davinci-resolve-mcp")
 logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
 logger.info(f"Detected platform: {get_platform()}")

package/src/server.py

@@ -11,7 +11,7 @@ Usage:
     python src/server.py --full       # Start the 377-tool granular server instead
 """
 
-VERSION = "4.13.2"
+VERSION = "4.13.4"
 
 import base64
 import os

package/src/utils/resolve_bridge.py

@@ -540,7 +540,11 @@ class _Handler(socketserver.StreamRequestHandler):
 
 
 class _Server(socketserver.ThreadingTCPServer):
-    allow_reuse_address = True
+    # On POSIX SO_REUSEADDR only lets a restart rebind past TIME_WAIT. On
+    # Windows it lets a second socket share a live port, so a stale bridge and a
+    # new one could both listen and the orphan check in `start` never fired
+    # (#278). There the port is claimed exclusively instead.
+    allow_reuse_address = os.name != "nt"
     daemon_threads = True
     address_family = socket.AF_INET
 
@@ -548,6 +552,11 @@ class _Server(socketserver.ThreadingTCPServer):
         self.bridge = bridge
         super().__init__(address, _Handler)
 
+    def server_bind(self) -> None:
+        if os.name == "nt":  # pragma: no cover - exercised on Windows
+            self.socket.setsockopt(socket.SOL_SOCKET, socket.SO_EXCLUSIVEADDRUSE, 1)
+        super().server_bind()
+
 
 class Bridge:
     """Owns the listener, the nonce cache, and the serialised operation lock."""

package/src/utils/resolve_bridge_client.py

@@ -155,6 +155,13 @@ class BridgeTransport:
             truncated.get("limit"),
         )
 
+    def _unavailable(self, exc: OSError) -> BridgeUnavailable:
+        return BridgeUnavailable(
+            "Cannot reach the in-Resolve bridge on "
+            f"{self.host}:{self.port} ({exc}). Start it from "
+            "Workspace > Scripts > resolve_bridge."
+        )
+
     def request(self, operation: str, arguments: Dict[str, Any]) -> Any:
         payload = {
             "protocol": _bridge.PROTOCOL_VERSION,
@@ -171,7 +178,15 @@ class BridgeTransport:
 
         with self._lock:
             try:
-                with socket.create_connection((self.host, self.port), timeout=self.timeout) as sock:
+                # A connect that times out means no bridge, never a dialog: the
+                # kernel completes the handshake even while a modal dialog blocks
+                # Resolve. Windows retries a refused loopback SYN for ~2 s, so a
+                # short timeout fires here before the refusal does (#278).
+                sock = socket.create_connection((self.host, self.port), timeout=self.timeout)
+            except OSError as exc:
+                raise self._unavailable(exc) from exc
+            try:
+                with sock:
                     sock.settimeout(self.timeout)
                     sock.sendall(line)
                     raw = sock.makefile("rb").readline(_bridge.MAX_REQUEST_BYTES + 1)
@@ -182,11 +197,7 @@ class BridgeTransport:
                     "which blocks its scripting API entirely",
                 ) from exc
             except OSError as exc:
-                raise BridgeUnavailable(
-                    "Cannot reach the in-Resolve bridge on "
-                    f"{self.host}:{self.port} ({exc}). Start it from "
-                    "Workspace > Scripts > resolve_bridge."
-                ) from exc
+                raise self._unavailable(exc) from exc
 
         if not raw:
             raise BridgeCallError("bridge_protocol_error", "bridge closed without replying")