molecule-ai/molecule-core
51
0
Fork 2
Code Issues 164 Pull Requests 155 Actions 11 Packages Projects Releases Wiki Activity

[main-red] molecule-ai/molecule-core: 3ed5aaa2a1 #2477

New Issue
Closed
opened 2026-06-09 06:07:20 +00:00 by gitea-actions · 1 comment
gitea-actions bot commented 2026-06-09 06:07:20 +00:00
Copy Link
Copy Source

Main is RED on molecule-ai/molecule-core at 3ed5aaa2a1

Commit: https://git.moleculesai.app/molecule-ai/molecule-core/commit/3ed5aaa2a1c168f8f0d758882c5f9ed8b4bcd4fe

Auto-filed by .gitea/workflows/main-red-watchdog.yml (Option C of the main-never-red directive). Per feedback_no_such_thing_as_flakes + feedback_fix_root_not_symptom: investigate the root cause; do NOT revert as a reflex. The watchdog itself never reverts.

Failed status contexts

  • Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push) — failure → logs
    • Failing after 4m33s
  • E2E Chat / E2E Chat (push) — failure → logs
    • Failing after 5m42s
  • publish-workspace-server-image / Production auto-deploy (push) — failure → logs
    • Failing after 4m19s
  • Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push) — failure → logs
    • Failing after 7m2s

Resolution path

  1. Read the failed logs (links above).
  2. If reproducible locally, fix forward in a PR targeting main.
  3. If the failure is a real flake — STOP. Per feedback_no_such_thing_as_flakes, intermittent failures are real bugs. Investigate to root cause; do not mark as flake.
  4. If the failure is blocking unrelated work for >1 hour, file a follow-up issue and assign someone. Do NOT revert without a human GO per feedback_prod_apply_needs_hongming_chat_go (branch protection is a prod surface).

Debug

{
  "all_contexts": [
    {
      "context": "ci-arm64-advisory / fast-checks (push)",
      "state": "pending"
    },
    {
      "context": "Block internal-flavored paths / Block forbidden paths (push)",
      "state": "success"
    },
    {
      "context": "CI / Python Lint & Test (push)",
      "state": "success"
    },
    {
      "context": "CI / Detect changes (push)",
      "state": "success"
    },
    {
      "context": "E2E API Smoke Test / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "E2E Chat / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "CI / Canvas (Next.js) (push)",
      "state": "success"
    },
    {
      "context": "Handlers Postgres Integration / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "CI / Shellcheck (E2E scripts) (push)",
      "state": "success"
    },
    {
      "context": "Harness Replays / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "CI / Canvas Deploy Status (push)",
      "state": "success"
    },
    {
      "context": "Lint forbidden tenant-env keys / Scan for repo-host token write into tenant workspace surface (push)",
      "state": "success"
    },
    {
      "context": "Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (push)",
      "state": "success"
    },
    {
      "context": "Harness Replays / Harness Replays (push)",
      "state": "success"
    },
    {
      "context": "E2E Staging Canvas (Playwright) / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "Secret scan / Scan diff for credential-shaped strings (push)",
      "state": "success"
    },
    {
      "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)",
      "state": "success"
    },
    {
      "context": "Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (push)",
      "state": "success"
    },
    {
      "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)",
      "state": "success"
    },
    {
      "context": "Ops Scripts Tests / Ops scripts (unittest) (push)",
      "state": "success"
    },
    {
      "context": "publish-workspace-server-image / build-and-push (push)",
      "state": "success"
    },
    {
      "context": "CI / Platform (Go) (push)",
      "state": "success"
    },
    {
      "context": "CI / all-required (push)",
      "state": "success"
    },
    {
      "context": "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push)",
      "state": "failure"
    },
    {
      "context": "E2E API Smoke Test / E2E API Smoke Test (push)",
      "state": "success"
    },
    {
      "context": "E2E Chat / E2E Chat (push)",
      "state": "failure"
    },
    {
      "context": "publish-workspace-server-image / Production auto-deploy (push)",
      "state": "failure"
    },
    {
      "context": "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push)",
      "state": "failure"
    }
  ],
  "branch": "main",
  "combined_state": "failure",
  "failed_contexts": [
    "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push)",
    "E2E Chat / E2E Chat (push)",
    "publish-workspace-server-image / Production auto-deploy (push)",
    "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push)"
  ],
  "recheck_combined_state": "failure",
  "recheck_failed_contexts": [
    "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push)",
    "E2E Chat / E2E Chat (push)",
    "publish-workspace-server-image / Production auto-deploy (push)",
    "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push)"
  ],
  "sha": "3ed5aaa2a1c168f8f0d758882c5f9ed8b4bcd4fe"
}

This issue is idempotent: the watchdog runs hourly at :05 and edits this body in place. When main returns to green, the watchdog will close this issue automatically with a "main returned to green" comment.

# Main is RED on `molecule-ai/molecule-core` at `3ed5aaa2a1` Commit: <https://git.moleculesai.app/molecule-ai/molecule-core/commit/3ed5aaa2a1c168f8f0d758882c5f9ed8b4bcd4fe> Auto-filed by `.gitea/workflows/main-red-watchdog.yml` (Option C of the [main-never-red directive](https://git.moleculesai.app/molecule-ai/molecule-core/issues/420)). Per `feedback_no_such_thing_as_flakes` + `feedback_fix_root_not_symptom`: investigate the root cause; do NOT revert as a reflex. The watchdog itself never reverts. ## Failed status contexts - **Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/304458/jobs/407256) - Failing after 4m33s - **E2E Chat / E2E Chat (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/304448/jobs/407240) - Failing after 5m42s - **publish-workspace-server-image / Production auto-deploy (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/304459/jobs/407259) - Failing after 4m19s - **Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/304458/jobs/407257) - Failing after 7m2s ## Resolution path 1. Read the failed logs (links above). 2. If reproducible locally, fix forward in a PR targeting `main`. 3. If the failure is a real flake — STOP. Per `feedback_no_such_thing_as_flakes`, intermittent failures are real bugs. Investigate to root cause; do not mark as flake. 4. If the failure is blocking unrelated work for >1 hour, file a follow-up issue and assign someone. Do NOT revert without a human GO per `feedback_prod_apply_needs_hongming_chat_go` (branch protection is a prod surface). ## Debug ```json { "all_contexts": [ { "context": "ci-arm64-advisory / fast-checks (push)", "state": "pending" }, { "context": "Block internal-flavored paths / Block forbidden paths (push)", "state": "success" }, { "context": "CI / Python Lint & Test (push)", "state": "success" }, { "context": "CI / Detect changes (push)", "state": "success" }, { "context": "E2E API Smoke Test / detect-changes (push)", "state": "success" }, { "context": "E2E Chat / detect-changes (push)", "state": "success" }, { "context": "CI / Canvas (Next.js) (push)", "state": "success" }, { "context": "Handlers Postgres Integration / detect-changes (push)", "state": "success" }, { "context": "CI / Shellcheck (E2E scripts) (push)", "state": "success" }, { "context": "Harness Replays / detect-changes (push)", "state": "success" }, { "context": "CI / Canvas Deploy Status (push)", "state": "success" }, { "context": "Lint forbidden tenant-env keys / Scan for repo-host token write into tenant workspace surface (push)", "state": "success" }, { "context": "Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (push)", "state": "success" }, { "context": "Harness Replays / Harness Replays (push)", "state": "success" }, { "context": "E2E Staging Canvas (Playwright) / detect-changes (push)", "state": "success" }, { "context": "Secret scan / Scan diff for credential-shaped strings (push)", "state": "success" }, { "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)", "state": "success" }, { "context": "Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (push)", "state": "success" }, { "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)", "state": "success" }, { "context": "Ops Scripts Tests / Ops scripts (unittest) (push)", "state": "success" }, { "context": "publish-workspace-server-image / build-and-push (push)", "state": "success" }, { "context": "CI / Platform (Go) (push)", "state": "success" }, { "context": "CI / all-required (push)", "state": "success" }, { "context": "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push)", "state": "failure" }, { "context": "E2E API Smoke Test / E2E API Smoke Test (push)", "state": "success" }, { "context": "E2E Chat / E2E Chat (push)", "state": "failure" }, { "context": "publish-workspace-server-image / Production auto-deploy (push)", "state": "failure" }, { "context": "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push)", "state": "failure" } ], "branch": "main", "combined_state": "failure", "failed_contexts": [ "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push)", "E2E Chat / E2E Chat (push)", "publish-workspace-server-image / Production auto-deploy (push)", "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push)" ], "recheck_combined_state": "failure", "recheck_failed_contexts": [ "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (push)", "E2E Chat / E2E Chat (push)", "publish-workspace-server-image / Production auto-deploy (push)", "Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (push)" ], "sha": "3ed5aaa2a1c168f8f0d758882c5f9ed8b4bcd4fe" } ``` _This issue is idempotent: the watchdog runs hourly at `:05` and edits this body in place. When `main` returns to green, the watchdog will close this issue automatically with a "main returned to green" comment._
agent-reviewer commented 2026-06-10 07:38:48 +00:00
Member
Copy Link
Copy Source

Closing as STALE-HISTORICAL (per the consolidated main-red RCA 2026-06-10; verified each before close). This [main-red] tracker fired at an OLD commit (3ed5aaa2a1) that main has long advanced past (now 436a3a34+). Its failing contexts all map to KNOWN/CAPTURED root-cause buckets — no orphan/undiagnosed cause:
• KI-013 Local-Provision-Lifecycle drift → FIXED via #2500 (merged) + #2490 (in-fix)
• staging-infra E2E (E2E Staging SaaS/Concierge/Platform-Boot) → operator-gated (+ cp#646)
• Production-auto-deploy / Railway prod-deploy → the DOMINANT cause across the cascade, LIVE on current main, captured in the CTO root-cause surface as a dedicated incident
• secret-scan gate (Scan-diff-for-credentials / repo-host-tokens) → security diagnosis in-flight
• E2E-Chat → tracked by #2506; Canvas-tabs-E2E → now GREEN on current main (resolved)
The cascade was ~3 recurring causes wearing 14 hats; the live ones are owned elsewhere. Closing to clear tracker noise.

Closing as STALE-HISTORICAL (per the consolidated main-red RCA 2026-06-10; verified each before close). This [main-red] tracker fired at an OLD commit (3ed5aaa2a1) that main has long advanced past (now 436a3a34+). Its failing contexts all map to KNOWN/CAPTURED root-cause buckets — no orphan/undiagnosed cause: • KI-013 Local-Provision-Lifecycle drift → FIXED via #2500 (merged) + #2490 (in-fix) • staging-infra E2E (E2E Staging SaaS/Concierge/Platform-Boot) → operator-gated (+ cp#646) • Production-auto-deploy / Railway prod-deploy → the DOMINANT cause across the cascade, LIVE on current main, captured in the CTO root-cause surface as a dedicated incident • secret-scan gate (Scan-diff-for-credentials / repo-host-tokens) → security diagnosis in-flight • E2E-Chat → tracked by #2506; Canvas-tabs-E2E → now GREEN on current main (resolved) The cascade was ~3 recurring causes wearing 14 hats; the live ones are owned elsewhere. Closing to clear tracker noise.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 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) hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2477
Delete Branch "%!s()"

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?