dosync 0.6.1__tar.gz → 0.6.2__tar.gz

{dosync-0.6.1 → dosync-0.6.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dosync
-Version: 0.6.1
+Version: 0.6.2
 Summary: The semantic layer between AI agents and physical devices
 Author-email: Rodrigo Giuliani <rgiuliani@dosync.dev>
 License-Expression: Apache-2.0

{dosync-0.6.1 → dosync-0.6.2}/dosync/__init__.py

@@ -13,5 +13,5 @@ The two numbers move independently on purpose:
   __version__           this implementation of the hub  (semver)
   __protocol_version__  the wire contract other implementations must match
 """
-__version__ = "0.6.1"
+__version__ = "0.6.2"
 __protocol_version__ = "0.4"

{dosync-0.6.1 → dosync-0.6.2}/dosync/server.py

@@ -12,7 +12,8 @@ import json
 import os
 import re
 from fastapi import Depends, FastAPI, HTTPException, Request, WebSocket, WebSocketDisconnect
-from fastapi.responses import FileResponse, HTMLResponse, PlainTextResponse
+from fastapi.responses import (FileResponse, HTMLResponse, JSONResponse,
+                               PlainTextResponse)
 from fastapi.staticfiles import StaticFiles
 from pydantic import BaseModel, field_validator
 
@@ -933,7 +934,26 @@ async def lifespan(app: FastAPI):
         log.warning("Could not flush the audit head on shutdown: %s", _fh_e)
     log.info("DoSync Hub shutting down")
 
+class _UTF8JSONResponse(JSONResponse):
+    """`application/json; charset=utf-8`, said out loud rather than assumed.
+
+    JSON is UTF-8 by definition and FastAPI therefore omits the charset — which
+    is correct and, for one widely used client, useless. Windows PowerShell 5.1
+    falls back to Latin-1 when a response does not declare one, so an operator
+    following this project's own Windows instructions saw
+    `read-only status query â device has no sensors` where an em dash belonged,
+    and would see the same for every accented character a deployment uses in a
+    device name.
+
+    Being right about the specification while a reader gets mojibake is the
+    kind of correctness this project has decided is not worth much.
+    """
+
+    media_type = "application/json; charset=utf-8"
+
+
 app = FastAPI(
+    default_response_class=_UTF8JSONResponse,
     title="DoSync Hub",
     description=(
         "DoSync Protocol — REST API\n\n"

{dosync-0.6.1 → dosync-0.6.2}/dosync.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dosync
-Version: 0.6.1
+Version: 0.6.2
 Summary: The semantic layer between AI agents and physical devices
 Author-email: Rodrigo Giuliani <rgiuliani@dosync.dev>
 License-Expression: Apache-2.0

{dosync-0.6.1 → dosync-0.6.2}/tests/test_server.py

@@ -199,3 +199,21 @@ def test_the_shipped_gpio_adapter_uses_the_current_endpoint():
     src = (REPO / "gpio_adapter.py").read_text()
     assert 'hub_post("/v1/intent/async"' in src
     assert 'hub_post("/v1/intent"' not in src
+
+
+def test_json_responses_declare_utf8():
+    """`read-only status query â device has no sensors to read`.
+
+    That is what a Windows operator saw following this project's own
+    instructions. JSON is UTF-8 by definition, so FastAPI omits the charset —
+    correct, and useless for Windows PowerShell 5.1, which falls back to
+    Latin-1 when a response does not declare one. Every em dash and every
+    accented character in a device name arrives mangled.
+
+    The README documents `Invoke-RestMethod` as the way to call this API from
+    Windows, so the tool it recommends was the one showing broken text.
+    """
+    response = client.get("/v1/status")
+    assert "charset=utf-8" in response.headers.get("content-type", "").lower(), (
+        "JSON responses do not declare their charset, so clients that guess "
+        "wrongly — PowerShell 5.1 among them — mangle every non-ASCII byte")