deepctl-telemetry 0.0.4__tar.gz → 0.0.6__tar.gz

{deepctl_telemetry-0.0.4 → deepctl_telemetry-0.0.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepctl-telemetry
-Version: 0.0.4
+Version: 0.0.6
 Summary: Opt-out phone-home telemetry for deepctl
 Author-email: Deepgram <devrel@deepgram.com>
 Maintainer-email: Deepgram <devrel@deepgram.com>

{deepctl_telemetry-0.0.4 → deepctl_telemetry-0.0.6}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "deepctl-telemetry"
-version = "0.0.4" # x-release-please-version
+version = "0.0.6" # x-release-please-version
 description = "Opt-out phone-home telemetry for deepctl"
 readme = "README.md"
 license = "MIT"

{deepctl_telemetry-0.0.4 → deepctl_telemetry-0.0.6}/src/deepctl_telemetry/__init__.py

@@ -10,4 +10,4 @@ __all__ = [
     "render_notice",
 ]
 
-__version__ = "0.0.4"  # x-release-please-version
+__version__ = "0.0.6"  # x-release-please-version

{deepctl_telemetry-0.0.4 → deepctl_telemetry-0.0.6}/src/deepctl_telemetry/client.py

@@ -103,13 +103,66 @@ def _read_cli_version() -> str:
     return importlib.metadata.version("deepctl")
 
 
+_MCP_NOISE_LOGGERS = frozenset(
+    {
+        "mcp.client.streamable_http",
+        "mcp.server.lowlevel.server",
+    }
+)
+
+
+def _is_mcp_transient_noise(event: Event) -> bool:
+    """Identify log events from the MCP SDK that are not actionable bugs.
+
+    `dg mcp` embeds the upstream `mcp` Python SDK, which logs to Sentry via
+    the logging integration whenever the upstream MCP server returns 5xx
+    (handled by the client) or the stdio peer closes mid-message (handled by
+    the server). Both are recovered internally. Surfacing them as Sentry
+    issues just creates triage cost for the DX team and hides real CLI bugs.
+
+    Any unhandled exception is kept regardless of logger.
+    """
+    if (event.get("logger") or "") not in _MCP_NOISE_LOGGERS:
+        return False
+    for exc in (event.get("exception") or {}).get("values") or []:
+        mechanism = exc.get("mechanism") or {}
+        if mechanism.get("handled") is False:
+            return False
+    return True
+
+
+def _is_broken_pipe(event: Event) -> bool:
+    """Identify events caused by writing to a closed/broken output stream.
+
+    When `dg mcp` runs as an MCP server, the host can close stdio while the
+    CLI is still finishing up. Any residual write (an advisory notification, a
+    console error message) then raises ``BrokenPipeError`` — or rich's
+    ``ValueError: I/O operation on closed file`` when the underlying stream is
+    already closed. Neither is an actionable CLI bug, so drop them rather than
+    page the DX team.
+    """
+    for exc in (event.get("exception") or {}).get("values") or []:
+        exc_type = exc.get("type") or ""
+        if exc_type == "BrokenPipeError":
+            return True
+        if exc_type == "ValueError" and "closed file" in (exc.get("value") or ""):
+            return True
+    return False
+
+
 def _scrub_event(event: Event, _hint: Hint) -> Event | None:
     """Drop request bodies, headers, and any user-identifying data.
 
     Sentry SDK already filters most PII via send_default_pii=False, but
     Auth tokens, project IDs, and file paths can still leak through
     breadcrumbs and exception messages. This is a defense-in-depth scrub.
+
+    Also drops known-noise events (see ``_is_mcp_transient_noise`` and
+    ``_is_broken_pipe``).
     """
+    if _is_mcp_transient_noise(event) or _is_broken_pipe(event):
+        return None
+
     request: dict[str, Any] = event.get("request") or {}
     if "headers" in request:
         request["headers"] = {}

{deepctl_telemetry-0.0.4 → deepctl_telemetry-0.0.6}/src/deepctl_telemetry.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepctl-telemetry
-Version: 0.0.4
+Version: 0.0.6
 Summary: Opt-out phone-home telemetry for deepctl
 Author-email: Deepgram <devrel@deepgram.com>
 Maintainer-email: Deepgram <devrel@deepgram.com>