Levandor

BE-3613 Algo Services py-mando Conformance

2 min read

BE-3613 Algo Services py-mando Conformance

Moves the two algo consumer services (Datadog catalog names bess-os-algo-optimization and bess-os-algo-forecast) onto the conformant py-mando wheel py-mando==1.16.1+dev.2691658359.14dfb3ad (Nexus dev, published from the MR !570 merge; see BE-3482 pymando Branch Review), replacing their forked logging/tracing code with the wheel’s surface incl. log_error. Code COMPLETE on both repos as of 2026-07-22; branches UNPUSHED, blocked only on VPN/Nexus access for the poetry gate. bess-forecast-as is explicitly OUT of scope.

For Agents

Status 2026-07-22: both feature/BE-3613 branches exist LOCALLY ONLY. Do not push or open MRs without Andras’s explicit per-MR yes (these repos may have different reviewer sets than mando; ask). Only the VPN-gated finish procedure below remains. Nexus index: https://nexus.cicdtst.alpiq.services/repository/pypi-group/simple/ (reachable only on VPN). A VPN watcher was killed twice; do NOT re-arm it, Andras will say when the VPN is up. Plan lineage: mando/.worktrees/BE-3482-pymando/docs/superpowers/plans/2026-07-09-plan2-service-dd-conformance.md with supersessions: branch = feature/BE-3613, wheel = the one above, forecast-as OUT.

Branch state (2026-07-22)

RepoBranchCommitsNotes
bess-optimizationfeature/BE-3613bb0555e pin bump, d47212d fork replacement, 71fb146 log_error adoptionauthor fixed to andras.lederer@alpiq.com; report at /Volumes/bandi/coding/poc/bess-optimization/.be3613-report.md
bess-forecast-day-aheadfeature/BE-361350231b6, 927e1e5, e1d5ade (same 3-commit pattern)additionally deletes the fork-test files test_tracing, test_fetch_ecs_metadata, test_logger; report at /Volumes/bandi/coding/poc/bess-forecast-day-ahead/.be3613-report.md

Both branches sit 3 commits off their repo’s origin/develop with the same shape: wheel pin bump, fork replacement, log_error adoption.

Finish procedure (VPN required)

Per repo, bess-optimization first (source: HANDOVER-error-handling-2026-07-22 section “BE-3613 finish procedure”):

  1. poetry lock --no-update && poetry install && poetry run pytest. Confirm REAL pass counts; fallout unlikely (migrations were py_compile + shim verified).
  2. Commit the lock as its OWN title-only commit (chore: refresh lock for py-mando bump); do not amend the pin commit.
  3. Push the branch (plain push, new branch) and verify with git ls-remote (RTK can fake-green a push).
  4. MRs only on Andras’s explicit yes.

Graph View

Backlinks