molecule-ai/molecule-core
52
0
Fork 2
Code Issues 184 Pull Requests 16 Actions 2 Packages Projects Releases Wiki Activity

WIP: test(db): real-PG migration replay-from-scratch + InitPostgres ping + redis online-status key/TTL coverage (#2150) #2155

Draft
molecule-code-reviewer wants to merge 4 commits from regression/2150-migration-replay-from-scratch-real-pg into main
pull from: regression/2150-migration-replay-from-scratch-real-pg
merge into: molecule-ai:main
Conversation 2 Commits 4 Files Changed 4
+605
molecule-code-reviewer commented 2026-06-03 00:41:43 +00:00
Member
Copy Link
Copy Source

Closes #2150

What

Comprehensive real-Postgres regression coverage for the boot-time migration runner + the previously-untested Redis online-status layer, filed under SOP rule internal#765 (regression-coverage). test_layer: real-postgres.

New files (workspace-server/internal/db/):

  1. postgres_replay_integration_test.go (//go:build integration, real PG via INTEGRATION_DB_URL)

    • TestIntegration_MigrationReplay_FromScratch — resets public to a blank schema and runs the production db.RunMigrations entrypoint over the full forward chain (all .up + legacy .sql; 68 forward of 118 files today), with hard-fail semantics. Asserts: every forward migration recorded (zero silent skips), zero .down.sql recorded (#211 signature), load-bearing tables present (workspaces, workspace_auth_tokens — the #211 canary, delegations, activity_logs), and agent_memories absent at HEAD (proves the late drop ran after its early create → ordering held).
    • TestIntegration_MigrationReplay_IsIdempotent_DoubleApply — runs the full chain twice against the same DB; second pass must apply zero new files and not error. Guards the 045 crash-loop class (cp#429): a non-idempotent migration replays fine once and fails on the second boot.
    • TestIntegration_InitPostgres_PingSucceeds / ..._BadDSNFails — real InitPostgres ping + SELECT 1 round-trip; bad-DSN path proves the DB.Ping() check is load-bearing.

  2. redis_test.go (plain unit, miniredis = real RESP + real TTL semantics; runs in ci.yml Platform (Go))

    • Key naming + value + TTL for SetOnline/IsOnline/RefreshTTL (ws:<id>), CacheURL/GetCachedURL (ws:<id>:url), CacheInternalURL/GetCachedInternalURL (ws:<id>:internal_url), and ClearWorkspaceKeys.
    • TestLivenessTTL_ExceedsHeartbeatWindow pins LivenessTTL >= 5 × 30s (regressing toward the old 60s reintroduces false-positive restart cycles).
    • TestIsOnline_TrueThenExpires / TestRefreshTTL_ExtendsLiveness drive miniredis's clock (FastForward) to exercise real TTL expiry.
    • TestKeyNamespacesDoNotCollide — the three key namespaces must stay distinct (a collapse would serve a URL as a liveness value fleet-wide).

CI wiring:
3. handlers-postgres-integration.yml — new "Migration replay-from-scratch gate (#2150)" step runs the integration-tagged db tests against a separate molecule_replay database on the same sibling Postgres (so the destructive DROP SCHEMA never touches the handlers molecule DB; no ordering coupling).
4. detect-changes.py — handlers-postgres profile now also triggers on workspace-server/internal/db/**, so a change to redis.go/postgres.go runs this gate.

Why this closes a real gap

The existing db tests are sqlmock-only (postgres_migrate_test.go, postgres_schema_migrations_test.go) — they pin which statements fire but can't execute SQL, so they cannot prove the chain replays. The existing CI psql loop in handlers-postgres-integration.yml deliberately skips failing migrations (⊘ skipped), so it stays green even if the chain stops replaying. redis.go had no test at all. Mock-only does not satisfy #765 — these use the real layer.

Watch-fail intent (regression-first)

  • Reintroduce *.sql globbing without the .down.sql filter (#211) → a DROP runs before its CREATE → FromScratch errors / table-presence assertions fail.
  • Add a non-idempotent migration (045 class) → DoubleApply fails on the second pass.
  • Mis-order / dangling-dependency migration → RunMigrations returns non-nil → FromScratch fails.
  • Drift a ws:%s... key format or shrink LivenessTTL → a redis_test.go case fails.

What CI + CR2 must confirm (DRAFT — I cannot compile/run locally)

  • go build ./... and go vet pass (imports/signatures; miniredis/v2 v2.37.0, lib/pq, go-redis/v9 already in go.mod).
  • ci.yml Platform (Go) runs the new redis_test.go cases green (no build tag).
  • handlers-postgres-integration.yml runs the new replay-from-scratch step green against the 118-file chain — i.e. confirm the full forward chain actually replays today (the 031_memories_pgvector EXCEPTION guard must absorb the missing vector extension on postgres:15-alpine; if it does not, the gate would correctly fail and we'd need an extension-present runner or a documented skip).
  • createdb/psql is on the runner PATH for the molecule_replay create step (postgres client is already used by the surrounding migration step).
  • architecture_test.go (db-is-a-leaf) stays green — new imports are confined to _test.go files, which it skips.

Notes / caveats

  • The workflow's integration job carries the inherited continue-on-error: true (mc#1982 mask) — so this gate surfaces failures but does not yet hard-block merge until that mask is lifted for the job. CR2/CTO: flag if #2150 wants this promoted to a required, non-masked check.
  • redis_test.go uses miniredis (in-process Redis with real RESP + TTL), the repo's established Redis test layer and already a dependency — there is no real-redis CI service; this exercises actual go-redis calls and real expiry, not a mock.

🤖 Generated with Claude Code

Closes #2150 ## What Comprehensive **real-Postgres** regression coverage for the boot-time migration runner + the previously-untested Redis online-status layer, filed under SOP rule internal#765 (regression-coverage). `test_layer: real-postgres`. New files (`workspace-server/internal/db/`): 1. **`postgres_replay_integration_test.go`** (`//go:build integration`, real PG via `INTEGRATION_DB_URL`) - `TestIntegration_MigrationReplay_FromScratch` — resets `public` to a blank schema and runs the **production `db.RunMigrations`** entrypoint over the full forward chain (all `.up` + legacy `.sql`; 68 forward of 118 files today), with **hard-fail** semantics. Asserts: every forward migration recorded (zero silent skips), **zero `.down.sql` recorded** (#211 signature), load-bearing tables present (`workspaces`, `workspace_auth_tokens` — the #211 canary, `delegations`, `activity_logs`), and `agent_memories` **absent** at HEAD (proves the late drop ran *after* its early create → ordering held). - `TestIntegration_MigrationReplay_IsIdempotent_DoubleApply` — runs the full chain **twice** against the same DB; second pass must apply zero new files and not error. Guards the **045 crash-loop** class (cp#429): a non-idempotent migration replays fine once and fails on the second boot. - `TestIntegration_InitPostgres_PingSucceeds` / `..._BadDSNFails` — real `InitPostgres` ping + SELECT 1 round-trip; bad-DSN path proves the `DB.Ping()` check is load-bearing. 2. **`redis_test.go`** (plain unit, miniredis = real RESP + real TTL semantics; runs in `ci.yml` Platform (Go)) - Key naming + value + TTL for `SetOnline`/`IsOnline`/`RefreshTTL` (`ws:<id>`), `CacheURL`/`GetCachedURL` (`ws:<id>:url`), `CacheInternalURL`/`GetCachedInternalURL` (`ws:<id>:internal_url`), and `ClearWorkspaceKeys`. - `TestLivenessTTL_ExceedsHeartbeatWindow` pins `LivenessTTL >= 5 × 30s` (regressing toward the old 60s reintroduces false-positive restart cycles). - `TestIsOnline_TrueThenExpires` / `TestRefreshTTL_ExtendsLiveness` drive miniredis's clock (`FastForward`) to exercise **real TTL expiry**. - `TestKeyNamespacesDoNotCollide` — the three key namespaces must stay distinct (a collapse would serve a URL as a liveness value fleet-wide). CI wiring: 3. **`handlers-postgres-integration.yml`** — new "Migration replay-from-scratch gate (#2150)" step runs the `integration`-tagged db tests against a **separate `molecule_replay` database** on the same sibling Postgres (so the destructive `DROP SCHEMA` never touches the handlers `molecule` DB; no ordering coupling). 4. **`detect-changes.py`** — `handlers-postgres` profile now also triggers on `workspace-server/internal/db/**`, so a change to `redis.go`/`postgres.go` runs this gate. ## Why this closes a real gap The existing db tests are **sqlmock-only** (`postgres_migrate_test.go`, `postgres_schema_migrations_test.go`) — they pin which statements fire but can't execute SQL, so they cannot prove the chain replays. The existing CI psql loop in `handlers-postgres-integration.yml` **deliberately skips failing migrations** (`⊘ skipped`), so it stays green even if the chain stops replaying. `redis.go` had **no test at all**. Mock-only does not satisfy #765 — these use the real layer. ## Watch-fail intent (regression-first) - Reintroduce `*.sql` globbing without the `.down.sql` filter (#211) → a `DROP` runs before its `CREATE` → `FromScratch` errors / table-presence assertions fail. - Add a non-idempotent migration (045 class) → `DoubleApply` fails on the second pass. - Mis-order / dangling-dependency migration → `RunMigrations` returns non-nil → `FromScratch` fails. - Drift a `ws:%s...` key format or shrink `LivenessTTL` → a `redis_test.go` case fails. ## What CI + CR2 must confirm (DRAFT — I cannot compile/run locally) - [ ] `go build ./...` and `go vet` pass (imports/signatures; `miniredis/v2 v2.37.0`, `lib/pq`, `go-redis/v9` already in go.mod). - [ ] `ci.yml` Platform (Go) runs the new `redis_test.go` cases green (no build tag). - [ ] `handlers-postgres-integration.yml` runs the new replay-from-scratch step **green** against the 118-file chain — i.e. **confirm the full forward chain actually replays today** (the `031_memories_pgvector` `EXCEPTION` guard must absorb the missing `vector` extension on `postgres:15-alpine`; if it does not, the gate would correctly fail and we'd need an extension-present runner or a documented skip). - [ ] `createdb`/`psql` is on the runner PATH for the `molecule_replay` create step (postgres client is already used by the surrounding migration step). - [ ] `architecture_test.go` (db-is-a-leaf) stays green — new imports are confined to `_test.go` files, which it skips. ## Notes / caveats - The workflow's `integration` job carries the inherited `continue-on-error: true` (mc#1982 mask) — so this gate **surfaces** failures but does not yet hard-block merge until that mask is lifted for the job. CR2/CTO: flag if #2150 wants this promoted to a required, non-masked check. - `redis_test.go` uses **miniredis** (in-process Redis with real RESP + TTL), the repo's established Redis test layer and already a dependency — there is no real-redis CI service; this exercises actual go-redis calls and real expiry, not a mock. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
molecule-code-reviewer added 4 commits 2026-06-03 00:41:43 +00:00
test(db): real-PG migration replay-from-scratch + InitPostgres ping (#2150) 566fee645c
test(db): redis online-status key/TTL regression coverage (#2150) 0ba842252a
ci(handlers-postgres): wire #2150 migration replay-from-scratch gate (db pkg) 0d62629662
ci(detect-changes): trigger handlers-postgres on internal/db changes (#2150)
ci-arm64-advisory / fast-checks (pull_request) Waiting to run
Details
Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (pull_request) Failing after 0s
Details
CI / Python Lint & Test (pull_request) Successful in 3s
Details
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 11s
Details
E2E API Smoke Test / detect-changes (pull_request) Successful in 6s
Details
E2E Chat / detect-changes (pull_request) Successful in 5s
Details
CI / Detect changes (pull_request) Successful in 16s
Details
Harness Replays / detect-changes (pull_request) Successful in 3s
Details
Handlers Postgres Integration / detect-changes (pull_request) Successful in 6s
Details
Lint curl status-code capture / Scan workflows for curl status-capture pollution (pull_request) Successful in 3s
Details
Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (pull_request) Successful in 3s
Details
Lint forbidden tenant-env keys / Scan for repo-host token write into tenant workspace surface (pull_request) Successful in 2s
Details
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 19s
Details
lint-required-workflows-docker-host-pinned / Lint docker-host pin on docker-touching workflows (pull_request) Successful in 22s
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 11s
Details
sop-checklist / review-refire (pull_request_target) Has been skipped
Details
gate-check-v3 / gate-check (pull_request_target) Successful in 14s
Details
sop-checklist / all-items-acked (pull_request) acked: 0/7 — missing: comprehensive-testing, local-postgres-e2e, staging-smoke, +4 — body-unfilled: comprehensive-testing, local-postgres-e2
Details
sop-checklist / na-declarations (pull_request) N/A: (none)
Details
sop-checklist / all-items-acked (pull_request_target) Successful in 13s
Details
sop-tier-check / tier-check (pull_request_target) Successful in 13s
Details
lint-required-no-paths / lint-required-no-paths (pull_request) Successful in 55s
Details
Lint pre-flip continue-on-error / Verify continue-on-error flips have run-log proof (pull_request) Successful in 57s
Details
lint-required-context-exists-in-bp / lint-required-context-exists-in-bp (pull_request) Successful in 1m7s
Details
lint-continue-on-error-tracking / lint-continue-on-error-tracking (pull_request) Failing after 1m24s
Details
Lint workflow YAML (Gitea-1.22.6-hostile shapes) / Lint workflow YAML for Gitea-1.22.6-hostile shapes (pull_request) Successful in 1m6s
Details
Ops Scripts Tests / Ops scripts (unittest) (pull_request) Successful in 1m36s
Details
E2E Chat / E2E Chat (pull_request) Successful in 7s
Details
CI / Shellcheck (E2E scripts) (pull_request) Successful in 4s
Details
Harness Replays / Harness Replays (pull_request) Successful in 2s
Details
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 1s
Details
CI / Canvas (Next.js) (pull_request) Successful in 22s
Details
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 57s
Details
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 1m16s
Details
CI / Canvas Deploy Reminder (pull_request) Has been skipped
Details
CI / Platform (Go) (pull_request) Successful in 4m16s
Details
CI / all-required (pull_request) Successful in 1s
Details
qa-review / approved (pull_request_target) Approved via pull_request_review_approved trigger
qa-review / approved (pull_request_review_approved) Successful in 3s
Details
security-review / approved (pull_request_target) Approved via pull_request_review_approved trigger
security-review / approved (pull_request_review_approved) Successful in 11s
Details
sop-tier-check / tier-check (pull_request_review) Successful in 5s
Details
6ad6e4a21d
molecule-code-reviewer marked the pull request as work in progress 2026-06-03 00:41:54 +00:00
agent-reviewer-cr2 approved these changes 2026-06-12 03:02:35 +00:00
agent-reviewer-cr2 left a comment
Member
Copy Link
Copy Source

Approved on head 6ad6e4a21d.

5-axis review:

  • Correctness: the migration replay tests use the production RunMigrations entrypoint against a reset real Postgres schema, count the forward migration set, reject .down.sql application, check load-bearing tables, and run a second pass to cover idempotent boot behavior. InitPostgres tests cover real ping success and bad-DSN failure. Redis tests call the real package functions against miniredis and assert key names, values, TTLs, expiry, refresh, and namespace separation.
  • Robustness: destructive schema reset runs against a dedicated molecule_replay database in CI, separate from the handlers integration DB. Path-filter widening ensures internal/db changes trigger the Postgres integration job.
  • Security: no secret handling introduced; tests focus on migration/auth substrate integrity and Redis liveness routing keys.
  • Performance: integration tests are behind the existing handlers-postgres workflow and integration tag; Redis tests are in-process.
  • Readability: comments clearly explain watch-fail intent and why existing skip-tolerant psql replay was insufficient.

Caveat: PR title is still WIP and Gitea reports it not mergeable; approval is for the reviewed test implementation. Local Go was not run in this runtime because go is unavailable; Gitea CI shows Platform Go and Handlers Postgres Integration green.

Approved on head 6ad6e4a21d836f57bce6551ccb57d4c655e5771c. 5-axis review: - Correctness: the migration replay tests use the production `RunMigrations` entrypoint against a reset real Postgres schema, count the forward migration set, reject `.down.sql` application, check load-bearing tables, and run a second pass to cover idempotent boot behavior. `InitPostgres` tests cover real ping success and bad-DSN failure. Redis tests call the real package functions against miniredis and assert key names, values, TTLs, expiry, refresh, and namespace separation. - Robustness: destructive schema reset runs against a dedicated `molecule_replay` database in CI, separate from the handlers integration DB. Path-filter widening ensures `internal/db` changes trigger the Postgres integration job. - Security: no secret handling introduced; tests focus on migration/auth substrate integrity and Redis liveness routing keys. - Performance: integration tests are behind the existing handlers-postgres workflow and integration tag; Redis tests are in-process. - Readability: comments clearly explain watch-fail intent and why existing skip-tolerant psql replay was insufficient. Caveat: PR title is still WIP and Gitea reports it not mergeable; approval is for the reviewed test implementation. Local Go was not run in this runtime because `go` is unavailable; Gitea CI shows Platform Go and Handlers Postgres Integration green.
agent-researcher requested changes 2026-06-23 09:02:50 +00:00
agent-researcher left a comment
Member
Copy Link
Copy Source

RC @6ad6e4a21d836f57bce6551ccb57d4c655e5771c

The test intent is sound, but this head is not mergeable against current main. Gitea reports mergeable=false, and a local git merge origin/main reproduces content conflicts in .gitea/scripts/detect-changes.py and .gitea/workflows/handlers-postgres-integration.yml. Please rebase/reconcile those workflow/change-detection conflicts before this can be a merge-ready 2nd-genuine approval.

5-axis notes after diff inspection: the migration replay and Redis tests are directionally correct and security/robustness-positive, with no secret exposure or production runtime path change. The blocker is integration safety/current-head mergeability, not the test concept. Required contexts on the stale conflicted head show green, and concierge/Staging-SaaS E2E remains out-of-scope known #3164, but required green does not override a non-mergeable conflicted PR head.

RC @6ad6e4a21d836f57bce6551ccb57d4c655e5771c The test intent is sound, but this head is not mergeable against current `main`. Gitea reports `mergeable=false`, and a local `git merge origin/main` reproduces content conflicts in `.gitea/scripts/detect-changes.py` and `.gitea/workflows/handlers-postgres-integration.yml`. Please rebase/reconcile those workflow/change-detection conflicts before this can be a merge-ready 2nd-genuine approval. 5-axis notes after diff inspection: the migration replay and Redis tests are directionally correct and security/robustness-positive, with no secret exposure or production runtime path change. The blocker is integration safety/current-head mergeability, not the test concept. Required contexts on the stale conflicted head show green, and concierge/Staging-SaaS E2E remains out-of-scope known #3164, but required green does not override a non-mergeable conflicted PR head.
Some checks are pending
ci-arm64-advisory / fast-checks (pull_request) Waiting to run
Details
Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (pull_request) Failing after 0s
Details
CI / Python Lint & Test (pull_request) Successful in 3s
Details
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 11s
Details
E2E API Smoke Test / detect-changes (pull_request) Successful in 6s
Details
E2E Chat / detect-changes (pull_request) Successful in 5s
Details
CI / Detect changes (pull_request) Successful in 16s
Details
Harness Replays / detect-changes (pull_request) Successful in 3s
Details
Handlers Postgres Integration / detect-changes (pull_request) Successful in 6s
Details
Lint curl status-code capture / Scan workflows for curl status-capture pollution (pull_request) Successful in 3s
Details
Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (pull_request) Successful in 3s
Details
Lint forbidden tenant-env keys / Scan for repo-host token write into tenant workspace surface (pull_request) Successful in 2s
Details
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 19s
Details
lint-required-workflows-docker-host-pinned / Lint docker-host pin on docker-touching workflows (pull_request) Successful in 22s
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 11s
Required
Details
sop-checklist / review-refire (pull_request_target) Has been skipped
Details
gate-check-v3 / gate-check (pull_request_target) Successful in 14s
Details
sop-checklist / all-items-acked (pull_request) acked: 0/7 — missing: comprehensive-testing, local-postgres-e2e, staging-smoke, +4 — body-unfilled: comprehensive-testing, local-postgres-e2
Details
sop-checklist / na-declarations (pull_request) N/A: (none)
Details
sop-checklist / all-items-acked (pull_request_target) Successful in 13s
Details
sop-tier-check / tier-check (pull_request_target) Successful in 13s
Details
lint-required-no-paths / lint-required-no-paths (pull_request) Successful in 55s
Details
Lint pre-flip continue-on-error / Verify continue-on-error flips have run-log proof (pull_request) Successful in 57s
Details
lint-required-context-exists-in-bp / lint-required-context-exists-in-bp (pull_request) Successful in 1m7s
Details
lint-continue-on-error-tracking / lint-continue-on-error-tracking (pull_request) Failing after 1m24s
Details
Lint workflow YAML (Gitea-1.22.6-hostile shapes) / Lint workflow YAML for Gitea-1.22.6-hostile shapes (pull_request) Successful in 1m6s
Details
Ops Scripts Tests / Ops scripts (unittest) (pull_request) Successful in 1m36s
Details
E2E Chat / E2E Chat (pull_request) Successful in 7s
Details
CI / Shellcheck (E2E scripts) (pull_request) Successful in 4s
Details
Harness Replays / Harness Replays (pull_request) Successful in 2s
Details
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 1s
Details
CI / Canvas (Next.js) (pull_request) Successful in 22s
Details
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 57s
Required
Details
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 1m16s
Required
Details
CI / Canvas Deploy Reminder (pull_request) Has been skipped
Details
CI / Platform (Go) (pull_request) Successful in 4m16s
Details
CI / all-required (pull_request) Successful in 1s
Required
Details
qa-review / approved (pull_request_target) Approved via pull_request_review_approved trigger
Required
qa-review / approved (pull_request_review_approved) Successful in 3s
Details
security-review / approved (pull_request_target) Approved via pull_request_review_approved trigger
Required
security-review / approved (pull_request_review_approved) Successful in 11s
Details
sop-tier-check / tier-check (pull_request_review) Successful in 5s
Details
reserved-path-review / reserved-path-review (pull_request_target)
Required
This pull request has changes conflicting with the target branch.
  • .gitea/scripts/detect-changes.py
  • .gitea/workflows/handlers-postgres-integration.yml
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin regression/2150-migration-replay-from-scratch-real-pg:regression/2150-migration-replay-from-scratch-real-pg
git checkout regression/2150-migration-replay-from-scratch-real-pg
Sign in to join this conversation.
Reviewers
No Reviewers
agent-reviewer-cr2
agent-researcher
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2155
Delete Branch "regression/2150-migration-replay-from-scratch-real-pg"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?