molecule-ai/molecule-core
52
0
Fork 2
Code Issues 189 Pull Requests 61 Actions 5 Packages Projects Releases Wiki Activity

[main-red] molecule-ai/molecule-core: 6137657704 #1636

New Issue
Closed
opened 2026-05-21 07:10:46 +00:00 by gitea-actions · 2 comments
gitea-actions bot commented 2026-05-21 07:10:46 +00:00
Copy Link
Copy Source

Main is RED on molecule-ai/molecule-core at 6137657704

Commit: https://git.moleculesai.app/molecule-ai/molecule-core/commit/6137657704b429ccdaf778a328896971c7efa9c0

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

  • publish-workspace-server-image / build-and-push (push) — failure → logs
    • Failing after 14s

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": "E2E Staging SaaS (full lifecycle) / pr-validate (push)",
      "state": "success"
    },
    {
      "context": "E2E API Smoke Test / E2E API Smoke Test (push)",
      "state": "pending"
    },
    {
      "context": "E2E Chat / E2E Chat (push)",
      "state": "pending"
    },
    {
      "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)",
      "state": "pending"
    },
    {
      "context": "Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (push)",
      "state": "pending"
    },
    {
      "context": "publish-workspace-server-image / build-and-push (push)",
      "state": "failure"
    },
    {
      "context": "publish-workspace-server-image / Production auto-deploy (push)",
      "state": "success"
    },
    {
      "context": "CI / Python Lint & Test (push)",
      "state": "success"
    },
    {
      "context": "Block internal-flavored paths / Block forbidden paths (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": "E2E Staging Canvas (Playwright) / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "Handlers Postgres Integration / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "Harness Replays / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (push)",
      "state": "success"
    },
    {
      "context": "Lint no tenant GITEA or GITHUB token write / Scan for repo-host token write into tenant workspace surface (push)",
      "state": "success"
    },
    {
      "context": "Secret scan / Scan diff for credential-shaped strings (push)",
      "state": "success"
    },
    {
      "context": "Sweep stale e2e-* orgs (staging) / Sweep e2e orgs (push)",
      "state": "success"
    },
    {
      "context": "CI / Platform (Go) (push)",
      "state": "success"
    },
    {
      "context": "CI / Shellcheck (E2E scripts) (push)",
      "state": "success"
    },
    {
      "context": "E2E Staging SaaS (full lifecycle) / E2E Staging SaaS (push)",
      "state": "success"
    },
    {
      "context": "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)",
      "state": "success"
    },
    {
      "context": "CI / Canvas (Next.js) (push)",
      "state": "success"
    },
    {
      "context": "Harness Replays / Harness Replays (push)",
      "state": "success"
    },
    {
      "context": "Continuous synthetic E2E (staging) / Synthetic E2E against staging (push)",
      "state": "pending"
    },
    {
      "context": "CI / all-required (push)",
      "state": "success"
    },
    {
      "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)",
      "state": "success"
    },
    {
      "context": "main-red-watchdog / watchdog (push)",
      "state": "pending"
    },
    {
      "context": "CI / Canvas Deploy Reminder (push)",
      "state": "success"
    }
  ],
  "branch": "main",
  "combined_state": "failure",
  "failed_contexts": [
    "publish-workspace-server-image / build-and-push (push)"
  ],
  "recheck_combined_state": "failure",
  "recheck_failed_contexts": [
    "publish-workspace-server-image / build-and-push (push)"
  ],
  "sha": "6137657704b429ccdaf778a328896971c7efa9c0"
}

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 `6137657704` Commit: <https://git.moleculesai.app/molecule-ai/molecule-core/commit/6137657704b429ccdaf778a328896971c7efa9c0> 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 - **publish-workspace-server-image / build-and-push (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/77547/jobs/0) - Failing after 14s ## 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": "E2E Staging SaaS (full lifecycle) / pr-validate (push)", "state": "success" }, { "context": "E2E API Smoke Test / E2E API Smoke Test (push)", "state": "pending" }, { "context": "E2E Chat / E2E Chat (push)", "state": "pending" }, { "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)", "state": "pending" }, { "context": "Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (push)", "state": "pending" }, { "context": "publish-workspace-server-image / build-and-push (push)", "state": "failure" }, { "context": "publish-workspace-server-image / Production auto-deploy (push)", "state": "success" }, { "context": "CI / Python Lint & Test (push)", "state": "success" }, { "context": "Block internal-flavored paths / Block forbidden paths (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": "E2E Staging Canvas (Playwright) / detect-changes (push)", "state": "success" }, { "context": "Handlers Postgres Integration / detect-changes (push)", "state": "success" }, { "context": "Harness Replays / detect-changes (push)", "state": "success" }, { "context": "Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (push)", "state": "success" }, { "context": "Lint no tenant GITEA or GITHUB token write / Scan for repo-host token write into tenant workspace surface (push)", "state": "success" }, { "context": "Secret scan / Scan diff for credential-shaped strings (push)", "state": "success" }, { "context": "Sweep stale e2e-* orgs (staging) / Sweep e2e orgs (push)", "state": "success" }, { "context": "CI / Platform (Go) (push)", "state": "success" }, { "context": "CI / Shellcheck (E2E scripts) (push)", "state": "success" }, { "context": "E2E Staging SaaS (full lifecycle) / E2E Staging SaaS (push)", "state": "success" }, { "context": "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)", "state": "success" }, { "context": "CI / Canvas (Next.js) (push)", "state": "success" }, { "context": "Harness Replays / Harness Replays (push)", "state": "success" }, { "context": "Continuous synthetic E2E (staging) / Synthetic E2E against staging (push)", "state": "pending" }, { "context": "CI / all-required (push)", "state": "success" }, { "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)", "state": "success" }, { "context": "main-red-watchdog / watchdog (push)", "state": "pending" }, { "context": "CI / Canvas Deploy Reminder (push)", "state": "success" } ], "branch": "main", "combined_state": "failure", "failed_contexts": [ "publish-workspace-server-image / build-and-push (push)" ], "recheck_combined_state": "failure", "recheck_failed_contexts": [ "publish-workspace-server-image / build-and-push (push)" ], "sha": "6137657704b429ccdaf778a328896971c7efa9c0" } ``` _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._
gitea-actions bot added the tier:high label 2026-05-21 07:10:46 +00:00
agent-researcher commented 2026-05-26 09:32:19 +00:00
Member
Copy Link
Copy Source

RCA — root cause

#1636 is isolated to the publish runner lane, not product/runtime code. The only failed context was publish-workspace-server-image / build-and-push, and it failed after 14s while product CI, staging E2E, CI / all-required, and production auto-deploy were green. That timing is before Docker image build/push work; the likely root is an early publish-runner environment/preflight failure: Docker daemon/socket access, Buildx/DOCKER_CONFIG permissions, or required publish credentials.

Evidence

  • Issue debug — all product CI and deploy gates were success; only publish-workspace-server-image / build-and-push was failure.
  • .gitea/workflows/publish-workspace-server-image.yml:75-83 — build-and-push runs on the dedicated publish runner pool, separate from normal CI.
  • .gitea/workflows/publish-workspace-server-image.yml:88-106 — first substantive step is docker info; it exits immediately if /var/run/docker.sock is inaccessible.
  • .gitea/workflows/publish-workspace-server-image.yml:119-136 — next early step requires AUTO_SYNC_TOKEN to pre-clone private manifest dependencies.
  • .gitea/workflows/publish-workspace-server-image.yml:143-153 and :160-161 — Buildx setup depends on a writable per-runner DOCKER_CONFIG; workflow comments at :51-57 document a real EACCES failure class on the publish runner.

Suggested fix

Route to publish-runner/CI-hygiene, not product rollback. Pull raw log for run 77547 and classify the exact first failing step: Docker daemon socket, AUTO_SYNC_TOKEN manifest clone, Buildx DOCKER_CONFIG permissions, or ECR/AWS auth. Durable fix belongs in the publish runner bootstrap: guarantee Docker daemon access, use a per-job writable DOCKER_CONFIG, validate AUTO_SYNC_TOKEN before clone, and include the failing preflight line in future main-red watchdog bodies.

Confidence

Medium — context isolation and 14s runtime strongly point to early publish-lane preflight, but raw logs are required to name the exact missing permission/credential.

## RCA — root cause `#1636` is isolated to the publish runner lane, not product/runtime code. The only failed context was `publish-workspace-server-image / build-and-push`, and it failed after 14s while product CI, staging E2E, `CI / all-required`, and production auto-deploy were green. That timing is before Docker image build/push work; the likely root is an early publish-runner environment/preflight failure: Docker daemon/socket access, Buildx/DOCKER_CONFIG permissions, or required publish credentials. ## Evidence - Issue debug — all product CI and deploy gates were `success`; only `publish-workspace-server-image / build-and-push` was `failure`. - `.gitea/workflows/publish-workspace-server-image.yml:75-83` — build-and-push runs on the dedicated `publish` runner pool, separate from normal CI. - `.gitea/workflows/publish-workspace-server-image.yml:88-106` — first substantive step is `docker info`; it exits immediately if `/var/run/docker.sock` is inaccessible. - `.gitea/workflows/publish-workspace-server-image.yml:119-136` — next early step requires `AUTO_SYNC_TOKEN` to pre-clone private manifest dependencies. - `.gitea/workflows/publish-workspace-server-image.yml:143-153` and `:160-161` — Buildx setup depends on a writable per-runner `DOCKER_CONFIG`; workflow comments at `:51-57` document a real EACCES failure class on the publish runner. ## Suggested fix Route to publish-runner/CI-hygiene, not product rollback. Pull raw log for run `77547` and classify the exact first failing step: Docker daemon socket, AUTO_SYNC_TOKEN manifest clone, Buildx `DOCKER_CONFIG` permissions, or ECR/AWS auth. Durable fix belongs in the publish runner bootstrap: guarantee Docker daemon access, use a per-job writable `DOCKER_CONFIG`, validate `AUTO_SYNC_TOKEN` before clone, and include the failing preflight line in future main-red watchdog bodies. ## Confidence Medium — context isolation and 14s runtime strongly point to early publish-lane preflight, but raw logs are required to name the exact missing permission/credential.
gitea-actions bot commented 2026-05-26 16:05:59 +00:00
Copy Link
Copy Source

main returned to green at SHA ca9fe8dbfca459f4b4a61f55dcd21fecae6c1b73 (https://git.moleculesai.app/molecule-ai/molecule-core/commit/ca9fe8dbfca459f4b4a61f55dcd21fecae6c1b73). Closing automatically. If the underlying root cause is not yet understood, reopen this issue and file a postmortem — green-by-flake is still a bug per feedback_no_such_thing_as_flakes.

`main` returned to green at SHA `ca9fe8dbfca459f4b4a61f55dcd21fecae6c1b73` (<https://git.moleculesai.app/molecule-ai/molecule-core/commit/ca9fe8dbfca459f4b4a61f55dcd21fecae6c1b73>). Closing automatically. If the underlying root cause is not yet understood, reopen this issue and file a postmortem — green-by-flake is still a bug per `feedback_no_such_thing_as_flakes`.
gitea-actions bot closed this issue 2026-05-26 16:05:59 +00:00
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 tier:high
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 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#1636
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?