ms-markets 2.2.8.dev32__tar.gz → 2.2.9__tar.gz

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/CHANGELOG.md

@@ -7,6 +7,23 @@ and this project follows versioned releases.
 
 ## [Unreleased]
 
+## [2.2.9] - 2026-10-11
+
+### Fixed
+
+- Give FastAPI startup an explicit 300-second MetaTables discovery scope for
+  canonical and pricing runtime attachment. A waking shared API previously
+  exhausted the ordinary 30-second budget and failed development rollout.
+  Startup still propagates attachment errors; normal request budgets are unchanged.
+
+### Changed
+
+- Document the shared MetaTables API 0.1.34 dependency for finalizing the
+  populated legacy TimescaleDB schema after the committed `0020` upgrade. Its
+  ownership-before-conversion repair preserves rows without adding internal
+  schema grants. Retry through the hosted migration Job; client requirements,
+  applied Alembic revisions, and development tables remain unchanged.
+
 ## [2.2.8] - 2026-10-11
 
 ### Fixed

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ms-markets
-Version: 2.2.8.dev32
+Version: 2.2.9
 Summary: Financial markets ORM, engines, and application management extensions for Main Sequence.
 Project-URL: Changelog, https://github.com/mainsequence-projects/MainSequenceMarkets/blob/main/CHANGELOG.md
 Project-URL: Source, https://github.com/mainsequence-projects/MainSequenceMarkets

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/docs/ADR/0046-legacy-0017-schema-bridge.md

@@ -48,6 +48,18 @@ Hosted execution remains the candidate image's migration Job, followed by API
 rollout only after successful catalog finalization. No local session runs hosted
 DDL. Both new revisions reject downgrade; future corrections use new revisions.
 
+
+Legacy TimescaleDB finalization also requires the shared **MetaTables API
+0.1.34** ownership-before-conversion repair. On TimescaleDB 2.10.2, converting
+a populated ordinary table and then reassigning it fails when the API login
+lacks `CREATE` on `_timescaledb_internal`. The API now transfers the ordinary
+table first, then converts it with `migrate_data`, in one transaction. This
+requires no new grant or application revision. If `0020` committed but
+finalization failed, deploy the repaired shared API and rerun the hosted Job at
+head; keep all existing application data and applied revisions. An already
+current development hypertable keeps its owner and rows. This is a server
+requirement; the Markets migration client remains 0.1.33.
+
 ## Validation
 
 The PostgreSQL regression fixture is a schema-only dump of the original `0017`

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/docs/fast_api/v1/index.md

@@ -3,6 +3,15 @@
 The local `apps/v1` FastAPI app exposes the migrated public asset registry
 surface for this repository.
 
+## Startup
+
+The deployment migration Job must finalize application tables before the API
+starts. FastAPI attaches the canonical and pricing runtimes in one
+`api_endpoint_scope(discovery_timeout=300)`, selected from its Environment. This
+bounded startup wait tolerates a waking or replacing shared MetaTables API;
+attachment errors still fail startup. The scope closes before serving requests,
+which keep their normal discovery budgets. Startup performs no schema migration.
+
 ## Scope
 
 This API is intentionally thin:

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/docs/knowledge/msm/migrations/index.md

@@ -106,6 +106,18 @@ finalization failed, inspect the actual schema and per-table errors, then rerun
 the same migration through a new deployment. Do not stamp, rewrite applied
 revisions, or downgrade to recover catalog state.
 
+
+Legacy TimescaleDB finalization also requires the shared **MetaTables API
+0.1.34** ownership-before-conversion repair. On TimescaleDB 2.10.2, converting
+a populated ordinary table and then reassigning it fails when the API login
+lacks `CREATE` on `_timescaledb_internal`. The API now transfers the ordinary
+table first, then converts it with `migrate_data`, in one transaction. This
+requires no new grant or application revision. If `0020` committed but
+finalization failed, deploy the repaired shared API and rerun the hosted Job at
+head; keep all existing application data and applied revisions. An already
+current development hypertable keeps its owner and rows. This is a server
+requirement; the Markets migration client remains 0.1.33.
+
 The runner carries changed, non-empty authored table descriptions, labels, and
 column descriptions, labels, and logical names in each finalization batch. An
 unchanged revision can therefore refresh catalog metadata without new DDL.

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/docs/releasing.md

@@ -153,6 +153,23 @@ and delegated requests from both static sites to their own environment APIs.
 A failed guard blocks rollout; investigate the drift or overlong values instead
 of bypassing the check. The bridge's new revisions are forward-only.
 
+
+Legacy TimescaleDB finalization also requires the shared **MetaTables API
+0.1.34** ownership-before-conversion repair. On TimescaleDB 2.10.2, converting
+a populated ordinary table and then reassigning it fails when the API login
+lacks `CREATE` on `_timescaledb_internal`. The API now transfers the ordinary
+table first, then converts it with `migrate_data`, in one transaction. This
+requires no new grant or application revision. If `0020` committed but
+finalization failed, deploy the repaired shared API and rerun the hosted Job at
+head; keep all existing application data and applied revisions. An already
+current development hypertable keeps its owner and rows. This is a server
+requirement; the Markets migration client remains 0.1.33.
+
+FastAPI startup also uses `api_endpoint_scope(discovery_timeout=300)` for its
+canonical and pricing runtime attachments. Discovery during shared-API wake or
+rollout previously exhausted the ordinary 30-second budget. Attachment errors
+still fail startup; the scope ends before normal request serving.
+
 ### Upgrading the migration client
 
 The project requires `mainsequence-metatable>=0.1.33,<0.2`; `uv.lock` and

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/docs/tutorial/01-assets.md

@@ -25,6 +25,11 @@ See [Migrations](../knowledge/msm/migrations/index.md)
 for the package registry, MetaTables Alembic provider, upgrade flow, schema
 finalization, and runtime attachment lifecycle.
 
+The hosted FastAPI app attaches its canonical and pricing runtimes inside one
+`api_endpoint_scope(discovery_timeout=300)` during startup. This permits the
+Environment's shared MetaTables API to wake without shortening the wait to
+30 seconds. Attachment failures still stop startup; request budgets stay unchanged.
+
 ## Runtime setup
 
 Production code normally initializes the required market MetaTables during

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/examples/msm/platform/metatable_migration_lifecycle.py

@@ -30,6 +30,11 @@ def main() -> None:
     print("Changed non-empty authored metadata refreshes without a new Alembic revision.")
     print("Empty metadata preserves existing values; equal-valued reruns avoid catalog writes.")
     print("Metadata finalization also requires the matching shared MetaTables API update.")
+    print("Legacy TimescaleDB finalization requires shared MetaTables API >=0.1.34.")
+    print("It re-owns ordinary tables before conversion, without new grants or row loss.")
+    print("After a committed 0020 and failed finalization, repair the API and rerun this Job.")
+    print("FastAPI startup uses the same 300s discovery scope for both runtime attachments.")
+    print("Attachment failures stop startup; normal request budgets stay unchanged.")
     print("INFO logs from metatables.migrations.runner report each phase's elapsed time.")
     print("Consumers migrate only their own providers, not the ms-markets provider.")
 

{ms_markets-2.2.8.dev32 → ms_markets-2.2.9}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ms-markets"
-version = "2.2.8.dev32"
+version = "2.2.9"
 description = "Financial markets ORM, engines, and application management extensions for Main Sequence."
 readme = "README.md"
 requires-python = ">=3.13,<3.14"

ms_markets-2.2.9/tests/msm/fastapi/v1/test_lifespan_discovery.py

@@ -0,0 +1,51 @@
+from __future__ import annotations
+
+import asyncio
+from contextlib import contextmanager
+
+import metatables.endpoint
+import pytest
+
+import apps.v1.main as main
+
+
+@pytest.mark.parametrize("failure_stage", [None, "markets", "pricing"])
+def test_startup_wait_scope_covers_both_attachments_and_preserves_failures(monkeypatch, failure_stage):
+    state = {"active": False, "budgets": [], "calls": []}
+    failure = RuntimeError("runtime attachment failed")
+    original = metatables.endpoint.api_endpoint_scope
+
+    @contextmanager
+    def observe_scope(*, discovery_timeout):
+        state["budgets"].append(discovery_timeout)
+        with original(discovery_timeout=discovery_timeout):
+            state["active"] = True
+            try:
+                yield
+            finally:
+                state["active"] = False
+
+    def attach(stage):
+        assert state["active"]
+        state["calls"].append(stage)
+        if failure_stage == stage:
+            raise failure
+
+    monkeypatch.setattr(main, "api_endpoint_scope", observe_scope)
+    monkeypatch.setattr(main, "ensure_apps_v1_runtime", lambda: attach("markets"))
+    monkeypatch.setattr(main, "ensure_apps_v1_pricing_runtime", lambda: attach("pricing"))
+
+    async def startup():
+        async with main.lifespan(None):
+            # Only startup gets the extended scope; normal serving does not.
+            assert not state["active"]
+
+    if failure_stage:
+        with pytest.raises(RuntimeError) as caught:
+            asyncio.run(startup())
+        assert caught.value is failure
+    else:
+        asyncio.run(startup())
+    assert state["budgets"] == [300]
+    assert not state["active"]
+    assert state["calls"] == (["markets"] if failure_stage == "markets" else ["markets", "pricing"])