code-analysis-client 1.6.241__tar.gz → 1.6.243__tar.gz

{code_analysis_client-1.6.241 → code_analysis_client-1.6.243}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-analysis-client
-Version: 1.6.241
+Version: 1.6.243
 Summary: Async JSON-RPC client for the code-analysis MCP server (mcp-proxy-adapter JsonRpcClient)
 Author-email: Vasiliy Zdanovskiy <vasilyvz@gmail.com>
 Requires-Python: >=3.10
@@ -80,8 +80,13 @@ Failures raise instead of returning an error envelope:
   and `.error` (always a structured error dict).
 * `JobTimeoutError` — only when a positive `timeout` elapses; the call detaches and
   the job keeps running server-side (`websocket.on_timeout` is `detach`).
-* `ClientValidationError` — the server refused the parameters (JSON-RPC `-32602`);
-  `details` carries the server's `violation` payload.
+* `ClientValidationError` — the server refused the parameters (JSON-RPC `-32602`),
+  answered at the top level or carried by the failed job of an in-process command
+  (same text `JSON-RPC error: <message> (code: -32602)`, `code` `VALIDATION_ERROR`);
+  `details` carries the server's error `data` (e.g. its `violation` payload). A
+  command the server refuses before starting it with its own error code (for
+  example `VALIDATION_ERROR` for an unknown `project_id`) raises it with that exact
+  `code` and the server's `data` as `details`.
 * `ValueError` — a negative `timeout` or a non-positive `poll_interval`, before
   anything is sent.
 

{code_analysis_client-1.6.241 → code_analysis_client-1.6.243}/README.md

@@ -68,8 +68,13 @@ Failures raise instead of returning an error envelope:
   and `.error` (always a structured error dict).
 * `JobTimeoutError` — only when a positive `timeout` elapses; the call detaches and
   the job keeps running server-side (`websocket.on_timeout` is `detach`).
-* `ClientValidationError` — the server refused the parameters (JSON-RPC `-32602`);
-  `details` carries the server's `violation` payload.
+* `ClientValidationError` — the server refused the parameters (JSON-RPC `-32602`),
+  answered at the top level or carried by the failed job of an in-process command
+  (same text `JSON-RPC error: <message> (code: -32602)`, `code` `VALIDATION_ERROR`);
+  `details` carries the server's error `data` (e.g. its `violation` payload). A
+  command the server refuses before starting it with its own error code (for
+  example `VALIDATION_ERROR` for an unknown `project_id`) raises it with that exact
+  `code` and the server's `data` as `details`.
 * `ValueError` — a negative `timeout` or a non-positive `poll_interval`, before
   anything is sent.
 

{code_analysis_client-1.6.241 → code_analysis_client-1.6.243}/code_analysis_client/client.py

@@ -37,6 +37,7 @@ from code_analysis_client.queue_wait import (
     QueuedJob,
     StatusHook,
     check_wait_arguments,
+    invalid_params_error,
     map_adapter_error,
     result_from_unified,
 )
@@ -71,14 +72,7 @@ def _remote_invalid_params_as_client_validation(
     if details.get("code") != -32602:
         return None
 
-    payload = details.get("data")
-    payload = payload if isinstance(payload, dict) else {}
-    field = payload.get("field")
-    return ClientValidationError(
-        str(error),
-        field=field if isinstance(field, str) else "command",
-        details=payload,
-    )
+    return invalid_params_error(str(error), details.get("data"))
 
 
 class CodeAnalysisAsyncClient:

{code_analysis_client-1.6.241 → code_analysis_client-1.6.243}/code_analysis_client/queue_wait.py

@@ -30,6 +30,7 @@ from mcp_proxy_adapter.client.jsonrpc_client.exceptions import (
 )
 
 from code_analysis_client.exceptions import (
+    ClientValidationError,
     CommandFailedError,
     JobFailedError,
     JobTimeoutError,
@@ -86,6 +87,36 @@ def _extract_inner_command_error(status_data: Dict[str, Any]) -> Any:
     return None
 
 
+def remote_error_text(message: Any, code: Any) -> str:
+    """Text of a server JSON-RPC error, identical to the adapter's ``ClientRemoteResponseError``.
+
+    ``"JSON-RPC error: <message> (code: <code>)"`` - used for an error carried by a failed job so
+    that it reads exactly like the same error answered at the top level.
+    """
+    return f"JSON-RPC error: {message} (code: {code})"
+
+
+def invalid_params_error(
+    message: str, data: Any, *, code: Optional[str] = None
+) -> ClientValidationError:
+    """Build the :class:`ClientValidationError` for a server refusal of a command's parameters.
+
+    The single constructor for the top-level -32602 refusal (``client.py``), a -32602 carried by a
+    failed job (``job_failure``) and a refused command-session open with the server's own error
+    code (``map_adapter_error``), so ``code`` / ``field`` / ``details`` have one shape: ``details``
+    is the server's error ``data`` object, ``field`` its ``field`` entry (else ``"command"``),
+    ``code`` ``VALIDATION_ERROR`` unless the server named its own code.
+    """
+    payload = data if isinstance(data, dict) else {}
+    field = payload.get("field")
+    return ClientValidationError(
+        message,
+        field=field if isinstance(field, str) else "command",
+        details=payload,
+        code=code,
+    )
+
+
 def command_failed(
     command: Optional[str], job_id: Optional[str], inner: Dict[str, Any]
 ) -> CommandFailedError:
@@ -100,8 +131,12 @@ def job_failure(
     job_id: Optional[str],
     status_data: Optional[Dict[str, Any]],
     terminal_event: Optional[Dict[str, Any]] = None,
-) -> JobFailedError:
-    """Build the :class:`JobFailedError` for a job that ended failed / stopped / cancelled.
+) -> Union[JobFailedError, ClientValidationError]:
+    """Build the error for a job that ended failed / stopped / cancelled.
+
+    A job whose structured error carries JSON-RPC ``-32602`` (the server validates after
+    enqueueing) yields :class:`ClientValidationError` exactly like a top-level refusal; every other
+    failure yields :class:`JobFailedError`.
 
     ``error`` is always the structured error object: the failed command's own error when the
     status payload carries one, else the queue-level error (a bare string is wrapped as
@@ -119,6 +154,10 @@ def job_failure(
         error = terminal_event.get("error")
     if not isinstance(error, dict):
         error = {"message": str(error) if error else f"job {status}", "status": status}
+    if error.get("code") == -32602:
+        return invalid_params_error(
+            remote_error_text(error.get("message"), -32602), error.get("data")
+        )
     return JobFailedError(job_id, error, status=status)
 
 
@@ -167,6 +206,11 @@ def map_adapter_error(
     * ``CommandSessionFailedError`` with a terminal event -> ``JobFailedError`` (structured error)
     * ``CommandSessionFailedError`` for a refused open (numeric ``code``) -> ``ClientRemoteResponseError``
       so the caller's JSON-RPC handling (-32602, -32601) is the same as on the HTTP path
+    * ``CommandSessionFailedError`` for a refused open carrying the server's own string error
+      ``code`` (the adapter forwards ``exc.code`` of the refusing exception, e.g. ``VALIDATION_ERROR``
+      from a command's ``validate_params`` before enqueue) -> ``ClientValidationError`` with that
+      exact ``code``, the server message and ``details`` = the server's ``data`` (the documented
+      refusal shape of :class:`ClientValidationError`)
     """
     if isinstance(exc, CommandSessionTimeoutError):
         details = exc.details if isinstance(exc.details, dict) else {}
@@ -205,6 +249,12 @@ def map_adapter_error(
                     "command": command,
                 },
             )
+        if isinstance(code, str) and code.strip():
+            return invalid_params_error(
+                str(details.get("error") or exc),
+                details.get("data"),
+                code=code.strip(),
+            )
     return None
 
 

code_analysis_client-1.6.243/code_analysis_client/version.txt

@@ -0,0 +1 @@
+1.6.243

{code_analysis_client-1.6.241 → code_analysis_client-1.6.243}/code_analysis_client.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-analysis-client
-Version: 1.6.241
+Version: 1.6.243
 Summary: Async JSON-RPC client for the code-analysis MCP server (mcp-proxy-adapter JsonRpcClient)
 Author-email: Vasiliy Zdanovskiy <vasilyvz@gmail.com>
 Requires-Python: >=3.10
@@ -80,8 +80,13 @@ Failures raise instead of returning an error envelope:
   and `.error` (always a structured error dict).
 * `JobTimeoutError` — only when a positive `timeout` elapses; the call detaches and
   the job keeps running server-side (`websocket.on_timeout` is `detach`).
-* `ClientValidationError` — the server refused the parameters (JSON-RPC `-32602`);
-  `details` carries the server's `violation` payload.
+* `ClientValidationError` — the server refused the parameters (JSON-RPC `-32602`),
+  answered at the top level or carried by the failed job of an in-process command
+  (same text `JSON-RPC error: <message> (code: -32602)`, `code` `VALIDATION_ERROR`);
+  `details` carries the server's error `data` (e.g. its `violation` payload). A
+  command the server refuses before starting it with its own error code (for
+  example `VALIDATION_ERROR` for an unknown `project_id`) raises it with that exact
+  `code` and the server's `data` as `details`.
 * `ValueError` — a negative `timeout` or a non-positive `poll_interval`, before
   anything is sent.
 

code_analysis_client-1.6.241/code_analysis_client/version.txt

@@ -1 +0,0 @@
-1.6.241