spatialdds 0.5.0__tar.gz → 0.5.1__tar.gz

{spatialdds-0.5.0 → spatialdds-0.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spatialdds
-Version: 0.5.0
+Version: 0.5.1
 Summary: SpatialDDS over plain HTTPS and a WebSocket: a client for the web binding (Appendix N), and the reference registry behind one command.
 Author: Open AR Cloud
 License: Apache-2.0
@@ -409,7 +409,17 @@ already worked changed. An embedder with its own source passes
 no write surface at all — which was unreachable before, when keeping
 subscribers connected meant exposing writes.
 
-## Not in 0.5.0
+0.5.1 fixes a defect in 0.4.0's seam that only its first real consumer could
+find: `make_app(command_registry=...)` silently replaced a registry that was
+empty at the time, because `Registry` was falsy when empty and the assignment
+used `or`. Since an embedder must have the app before it can build the backend
+that supplies the handlers, passing an empty registry and filling it a few
+lines later is the normal shape — and every one of those registrations went to
+an object the app had already discarded. If you called `register()` before
+`make_app()`, 0.4.0 and 0.5.0 worked; if you called it after, the command lane
+advertised nothing and refused every POST.
+
+## Not in 0.5.1
 
 Stated so nobody waits for them: no async API, no caching beyond ETag
 revalidation, no retry policy, no MCAP tooling beyond the journal the server

{spatialdds-0.5.0 → spatialdds-0.5.1}/README.md

@@ -385,7 +385,17 @@ already worked changed. An embedder with its own source passes
 no write surface at all — which was unreachable before, when keeping
 subscribers connected meant exposing writes.
 
-## Not in 0.5.0
+0.5.1 fixes a defect in 0.4.0's seam that only its first real consumer could
+find: `make_app(command_registry=...)` silently replaced a registry that was
+empty at the time, because `Registry` was falsy when empty and the assignment
+used `or`. Since an embedder must have the app before it can build the backend
+that supplies the handlers, passing an empty registry and filling it a few
+lines later is the normal shape — and every one of those registrations went to
+an object the app had already discarded. If you called `register()` before
+`make_app()`, 0.4.0 and 0.5.0 worked; if you called it after, the command lane
+advertised nothing and refused every POST.
+
+## Not in 0.5.1
 
 Stated so nobody waits for them: no async API, no caching beyond ETag
 revalidation, no retry policy, no MCAP tooling beyond the journal the server

{spatialdds-0.5.0 → spatialdds-0.5.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "spatialdds"
-version = "0.5.0"
+version = "0.5.1"
 description = "SpatialDDS over plain HTTPS and a WebSocket: a client for the web binding (Appendix N), and the reference registry behind one command."
 readme = "README.md"
 requires-python = ">=3.9"

{spatialdds-0.5.0 → spatialdds-0.5.1}/spatialdds/__init__.py

@@ -37,7 +37,7 @@ __all__ = [
     "content_manifest", "geo_anchor", "service_uri", "content_uri",
 ]
 
-__version__ = "0.5.0"
+__version__ = "0.5.1"
 #: The SpatialDDS-spec commit whose Appendix N and generated artifacts this
 #: package implements. Package versions and specification versions move
 #: independently; this is the one that says what the wire looks like.

{spatialdds-0.5.0 → spatialdds-0.5.1}/spatialdds/server/commands.py

@@ -127,5 +127,11 @@ class Registry:
     def types(self) -> list[str]:
         return sorted(self._handlers)
 
-    def __bool__(self) -> bool:
-        return bool(self._handlers)
+    # No `__bool__`. It returned `bool(self._handlers)`, which reads as a
+    # convenience and was a trap: `make_app` had `command_registry or
+    # Registry()`, so an empty registry -- the normal thing to pass, since an
+    # embedder needs the app before it can build the handlers -- was silently
+    # replaced by a fresh one, and every later `register()` was lost. Nothing
+    # else ever used the truthiness. A class whose emptiness is a legitimate
+    # state should not make `or` mean something surprising, so the method is
+    # gone rather than documented around.

{spatialdds-0.5.0 → spatialdds-0.5.1}/spatialdds/server/gw_http.py

@@ -876,7 +876,16 @@ def make_app(state: gateway.State, base: str, token: str | None,
     # The N.6 seam. Empty is the normal state: a gateway serving a recording
     # has no verbs, and N.6 says a suite MUST NOT require a command surface
     # to exist. An embedder registers handlers on this.
-    app["commands"] = command_registry or commands.Registry()
+    # `is not None`, not `or`. An empty registry is the normal thing to pass:
+    # an embedder needs the app before it can build the backend that supplies
+    # the handlers, so it passes a registry and populates it a few lines
+    # later. With `or` that registry was silently replaced -- `Registry` used
+    # to be falsy when empty -- and every later `register()` went to an object
+    # the app had already thrown away. Found by the web bridge, whose command
+    # lane advertised nothing and refused every POST while its own registry
+    # held the handler.
+    app["commands"] = (command_registry if command_registry is not None
+                       else commands.Registry())
     app["journal"] = journal
     app["subs"] = {}
     app["assets"] = assets

{spatialdds-0.5.0 → spatialdds-0.5.1}/spatialdds.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spatialdds
-Version: 0.5.0
+Version: 0.5.1
 Summary: SpatialDDS over plain HTTPS and a WebSocket: a client for the web binding (Appendix N), and the reference registry behind one command.
 Author: Open AR Cloud
 License: Apache-2.0
@@ -409,7 +409,17 @@ already worked changed. An embedder with its own source passes
 no write surface at all — which was unreachable before, when keeping
 subscribers connected meant exposing writes.
 
-## Not in 0.5.0
+0.5.1 fixes a defect in 0.4.0's seam that only its first real consumer could
+find: `make_app(command_registry=...)` silently replaced a registry that was
+empty at the time, because `Registry` was falsy when empty and the assignment
+used `or`. Since an embedder must have the app before it can build the backend
+that supplies the handlers, passing an empty registry and filling it a few
+lines later is the normal shape — and every one of those registrations went to
+an object the app had already discarded. If you called `register()` before
+`make_app()`, 0.4.0 and 0.5.0 worked; if you called it after, the command lane
+advertised nothing and refused every POST.
+
+## Not in 0.5.1
 
 Stated so nobody waits for them: no async API, no caching beyond ETag
 revalidation, no retry policy, no MCAP tooling beyond the journal the server