ms-markets 2.2.6.dev19__tar.gz → 2.2.6.dev21__tar.gz

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/CHANGELOG.md

@@ -23,6 +23,20 @@ and this project follows versioned releases.
 
 ### Changed
 
+- Requires `mainsequence-metatable>=0.1.28,<0.2`; the lock and exported
+  `requirements.txt` select 0.1.28. Changes in MetaTables 0.1.28
+  ([MetaTables#49](https://github.com/mainsequence-projects/MetaTables/pull/49)):
+  - The client finalizes at most 10 tables per request, the Alembic version
+    table first. A rerun of the migration Job finalizes whatever an
+    interrupted run left. Finalizing all 62 ms-markets tables in one request
+    ran past the hosted request limit, so the migration could never finish
+    ([MetaTables#46](https://github.com/mainsequence-projects/MetaTables/issues/46)).
+  - The hosted API reuses connections and serves concurrent requests on more
+    resources, so a long request no longer leaves it refusing connections
+    ([MetaTables#45](https://github.com/mainsequence-projects/MetaTables/issues/45)).
+  - A busy API answers `503` `database_connections_busy` with `Retry-After`;
+    nothing ran, and the call can be retried.
+  - The vendored MetaTables agent skills are refreshed to 0.1.28.
 - Requires `mainsequence-metatable>=0.1.27,<0.2`; the lock and exported
   `requirements.txt` select 0.1.27. Changes in MetaTables 0.1.27
   ([MetaTables#44](https://github.com/mainsequence-projects/MetaTables/pull/44)):
@@ -74,6 +88,17 @@ and this project follows versioned releases.
   They run as their own workload Users, and MetaTables API discovery failed
   without that access: "No visible FastAPI deployment named 'metatables'",
   then "Cannot verify the Environment of every visible API deployment".
+- `msm_portfolios.utils.get_portfolios_logger()` returns the logger bound with
+  `sub_application="portfolios"`. It discarded the result of `.bind()` and
+  returned the unbound SDK logger, so `msm_portfolios.utils.logger` and the
+  `msm_portfolios.configuration` logger never carried the binding.
+- `examples/msm_portfolios/portfolio_equal_weights_prepare_schema.py` runs the
+  dynamic Alembic revision and upgrade through the `metatables migrations` CLI.
+  It invoked `python -m mainsequence migrations ...`, which the SDK no longer
+  provides, so schema preparation failed unless `--check-only` was set.
+- Removed a stray module-level developer note from
+  `msm_portfolios/configuration.py` that referenced the retired SDK
+  `data_publishing` skill by a local absolute path.
 
 ## [2.2.5] - 2026-10-04
 

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ms-markets
-Version: 2.2.6.dev19
+Version: 2.2.6.dev21
 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
@@ -227,7 +227,7 @@ Requires-Python: <3.14,>=3.13
 Requires-Dist: alembic>=1.18.4
 Requires-Dist: cachetools
 Requires-Dist: fastapi>=0.136.3
-Requires-Dist: mainsequence-metatable<0.2,>=0.1.27
+Requires-Dist: mainsequence-metatable<0.2,>=0.1.28
 Requires-Dist: mainsequence<10,>=9.0.19
 Requires-Dist: numpy
 Requires-Dist: pandas
@@ -385,7 +385,7 @@ Recommended entry points:
 ## Quick Start
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.19,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.27,<0.2`, which is imported
+the MetaTables client `mainsequence-metatable>=0.1.28,<0.2`, which is imported
 as `metatables`. SDK 8 and earlier are not supported; install a 1.x
 `ms-markets` release when maintaining an SDK 8 project. See
 [ADR 0043](https://mainsequence-projects.github.io/MainSequenceMarkets/ADR/0043-sdk-9-metatables-client-hard-cut/)
@@ -503,7 +503,7 @@ The core stack starts with:
 
 - `mainsequence>=9.0.19,<10` for identity, login, Git source context,
   CodeRepository, jobs, and agents
-- `mainsequence-metatable>=0.1.27,<0.2` (import `metatables`) for MetaTables,
+- `mainsequence-metatable>=0.1.28,<0.2` (import `metatables`) for MetaTables,
   time-index table updaters, governed compiled SQL, and application-owned
   Alembic migrations
 - `SQLAlchemy` for market-domain ORM models

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/README.md

@@ -108,7 +108,7 @@ Recommended entry points:
 ## Quick Start
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.19,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.27,<0.2`, which is imported
+the MetaTables client `mainsequence-metatable>=0.1.28,<0.2`, which is imported
 as `metatables`. SDK 8 and earlier are not supported; install a 1.x
 `ms-markets` release when maintaining an SDK 8 project. See
 [ADR 0043](https://mainsequence-projects.github.io/MainSequenceMarkets/ADR/0043-sdk-9-metatables-client-hard-cut/)
@@ -226,7 +226,7 @@ The core stack starts with:
 
 - `mainsequence>=9.0.19,<10` for identity, login, Git source context,
   CodeRepository, jobs, and agents
-- `mainsequence-metatable>=0.1.27,<0.2` (import `metatables`) for MetaTables,
+- `mainsequence-metatable>=0.1.28,<0.2` (import `metatables`) for MetaTables,
   time-index table updaters, governed compiled SQL, and application-owned
   Alembic migrations
 - `SQLAlchemy` for market-domain ORM models

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/docs/fast_api/v1/index.md

@@ -173,7 +173,7 @@ push alone as deployment success.
 
 Runtime dependencies must be resolvable from the backend build environment.
 The published `ms-markets` 2.x package therefore declares
-`mainsequence>=9.0.19,<10` and `mainsequence-metatable>=0.1.27,<0.2` without
+`mainsequence>=9.0.19,<10` and `mainsequence-metatable>=0.1.28,<0.2` without
 exact patch pins. The lower bounds enforce the SDK 9 and MetaTables client
 extraction hard cut and the SDK request identity that the platform's current
 caller assertions require (SDK 9.0.18 and later), while the project lock and exported runtime requirements

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/docs/getting-started.md

@@ -1,7 +1,7 @@
 # Getting Started
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.19,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.27,<0.2` (imported as
+the MetaTables client `mainsequence-metatable>=0.1.28,<0.2` (imported as
 `metatables`). It cannot run against an SDK 8 or earlier contract and does not
 provide compatibility aliases or a mixed-version mode. Install a 1.x
 `ms-markets` release when maintaining an SDK 8 project.

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/docs/knowledge/msm/platform/metatable_migrations.md

@@ -110,7 +110,7 @@ history is the Alembic revision graph plus the provider's version table.
 
 ## Client Requirement
 
-The implementation requires `mainsequence-metatable>=0.1.27,<0.2` with
+The implementation requires `mainsequence-metatable>=0.1.28,<0.2` with
 `mainsequence>=9.0.19,<10`. The client exposes `AlembicMetaTableMigration`,
 `AlembicVersionMetaTable`, application-owned Alembic execution, and the command
 shape where

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/examples/msm_portfolios/portfolio_equal_weights_prepare_schema.py

@@ -2,6 +2,7 @@ from __future__ import annotations
 
 import argparse
 import os
+import shutil
 import subprocess
 import sys
 from collections.abc import Sequence
@@ -130,7 +131,7 @@ def prepare_equal_weight_portfolio_schema(
             revision_message=revision_message,
         )
         before_revision_files = _migration_revision_files()
-        _run_mainsequence(
+        _run_metatables(
             [
                 "migrations",
                 "revision",
@@ -155,7 +156,7 @@ def prepare_equal_weight_portfolio_schema(
     print_detail("dynamic_revision_file", revision_file)
 
     print_step(4, "Applying the dynamic migration revision.")
-    _run_mainsequence(
+    _run_metatables(
         [
             "migrations",
             "upgrade",
@@ -250,14 +251,14 @@ def _active_version_directory() -> Path:
     return Path(str(traversable))
 
 
-def _run_mainsequence(
+def _run_metatables(
     args: list[str],
     *,
     env: dict[str, str],
     allow_failure: bool = False,
 ) -> subprocess.CompletedProcess[str]:
     command_env = _command_env(env)
-    command = [sys.executable, "-m", "mainsequence", *args]
+    command = [_metatables_executable(), *args]
     print_detail("command", " ".join(command))
     result = subprocess.run(
         command,
@@ -271,6 +272,16 @@ def _run_mainsequence(
     return result
 
 
+def _metatables_executable() -> str:
+    candidate = Path(sys.executable).with_name("metatables")
+    if candidate.is_file():
+        return str(candidate)
+    executable = shutil.which("metatables")
+    if executable is None:
+        raise RuntimeError("The metatables CLI is not installed in this Python environment.")
+    return executable
+
+
 def _command_env(extra_env: dict[str, str]) -> dict[str, str]:
     env = os.environ.copy()
     env.update(extra_env)

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ms-markets"
-version = "2.2.6.dev19"
+version = "2.2.6.dev21"
 description = "Financial markets ORM, engines, and application management extensions for Main Sequence."
 readme = "README.md"
 requires-python = ">=3.13,<3.14"
@@ -37,7 +37,7 @@ dependencies = [
   "cachetools",
   "fastapi>=0.136.3",
   "mainsequence>=9.0.19,<10",
-  "mainsequence-metatable>=0.1.27,<0.2",
+  "mainsequence-metatable>=0.1.28,<0.2",
   "numpy",
   "pandas",
   "pip>=26.1.1",

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/src/msm_portfolios/configuration.py

@@ -580,11 +580,3 @@ class PortfolioConfiguration(PortfolioConfigBaseModel):
         ...,
         description="Defines portfolio metadata used when syncing to the markets platform.",
     )
-
-
-"""
-be sure to include in meta_tables 
-/Users/jose/code/MainSequenceClientSide/mainsequence-sdk/agent_scaffold/skills/data_publishing
-
-how to migrate or add another skill inside of data_publishing for migrating metatables
-"""

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/src/msm_portfolios/utils.py

@@ -4,8 +4,7 @@ from mainsequence import logger as _mainsequence_logger
 
 
 def get_portfolios_logger():
-    _mainsequence_logger.bind(sub_application="portfolios")
-    return _mainsequence_logger
+    return _mainsequence_logger.bind(sub_application="portfolios")
 
 
 logger = get_portfolios_logger()

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/tests/msm/test_package_metadata.py

@@ -39,8 +39,8 @@ def test_package_metadata_enforces_sdk_9_floor_without_exact_patch_pin() -> None
 def test_package_metadata_requires_extracted_metatables_client() -> None:
     requirement = _requirement("mainsequence-metatable")
 
-    assert Version("0.1.26") not in requirement.specifier
-    assert Version("0.1.27") in requirement.specifier
+    assert Version("0.1.27") not in requirement.specifier
+    assert Version("0.1.28") in requirement.specifier
     assert Version("0.1.99") in requirement.specifier
     assert Version("0.2.0") not in requirement.specifier
     assert all(specifier.operator != "==" for specifier in requirement.specifier)

{ms_markets-2.2.6.dev19 → ms_markets-2.2.6.dev21}/tests/msm_portfolios/examples/test_equal_weight_portfolio_schema.py

@@ -237,7 +237,7 @@ def test_prepare_schema_runs_upgrade_when_metadata_already_exists(
     )
     monkeypatch.setattr(
         prep,
-        "_run_mainsequence",
+        "_run_metatables",
         lambda args, *, env, allow_failure=False: commands.append((args, env)),
     )
 

ms_markets-2.2.6.dev21/tests/msm_portfolios/test_portfolios_logger.py

@@ -0,0 +1,12 @@
+from __future__ import annotations
+
+import structlog
+
+from msm_portfolios import utils
+
+
+def test_portfolios_logger_binds_sub_application() -> None:
+    assert structlog.get_context(utils.get_portfolios_logger()).get("sub_application") == (
+        "portfolios"
+    )
+    assert structlog.get_context(utils.logger).get("sub_application") == "portfolios"