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

[main-red] molecule-ai/molecule-core: 9981a5099a #1656

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

Main is RED on molecule-ai/molecule-core at 9981a5099a

Commit: https://git.moleculesai.app/molecule-ai/molecule-core/commit/9981a5099a61836c296b82947ead0721affbf4c5

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

  • Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push) — failure → logs
    • Failing after 6s
  • Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push) — failure → logs
    • Failing after 4m41s

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 Chat / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "Handlers Postgres Integration / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "E2E Staging Canvas (Playwright) / detect-changes (push)",
      "state": "success"
    },
    {
      "context": "Lint curl status-code capture / Scan workflows for curl status-capture pollution (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": "Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (push)",
      "state": "success"
    },
    {
      "context": "lint-required-workflows-docker-host-pinned / Lint docker-host pin on docker-touching workflows (push)",
      "state": "success"
    },
    {
      "context": "Secret scan / Scan diff for credential-shaped strings (push)",
      "state": "success"
    },
    {
      "context": "CI / Shellcheck (E2E scripts) (push)",
      "state": "success"
    },
    {
      "context": "E2E API Smoke Test / E2E API Smoke Test (push)",
      "state": "success"
    },
    {
      "context": "E2E Chat / E2E Chat (push)",
      "state": "success"
    },
    {
      "context": "lint-continue-on-error-tracking / lint-continue-on-error-tracking (push)",
      "state": "success"
    },
    {
      "context": "Lint workflow YAML (Gitea-1.22.6-hostile shapes) / Lint workflow YAML for Gitea-1.22.6-hostile shapes (push)",
      "state": "success"
    },
    {
      "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)",
      "state": "success"
    },
    {
      "context": "publish-workspace-server-image / build-and-push (push)",
      "state": "success"
    },
    {
      "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)",
      "state": "success"
    },
    {
      "context": "CI / Platform (Go) (push)",
      "state": "success"
    },
    {
      "context": "CI / Canvas (Next.js) (push)",
      "state": "success"
    },
    {
      "context": "CI / Canvas Deploy Reminder (push)",
      "state": "success"
    },
    {
      "context": "CI / all-required (push)",
      "state": "success"
    },
    {
      "context": "publish-workspace-server-image / Production auto-deploy (push)",
      "state": "success"
    },
    {
      "context": "gate-check-v3 / gate-check (push)",
      "state": "success"
    },
    {
      "context": "Sweep stale Cloudflare DNS records / Sweep CF orphans (push)",
      "state": "success"
    },
    {
      "context": "ci-required-drift / drift (push)",
      "state": "success"
    },
    {
      "context": "Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push)",
      "state": "failure"
    },
    {
      "context": "Sweep stale Cloudflare Tunnels / Sweep CF tunnels (push)",
      "state": "success"
    },
    {
      "context": "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)",
      "state": "pending"
    },
    {
      "context": "Sweep stale e2e-* orgs (staging) / Sweep e2e orgs (push)",
      "state": "success"
    },
    {
      "context": "Continuous synthetic E2E (staging) / Synthetic E2E against staging (push)",
      "state": "pending"
    },
    {
      "context": "main-red-watchdog / watchdog (push)",
      "state": "pending"
    }
  ],
  "branch": "main",
  "combined_state": "failure",
  "failed_contexts": [
    "Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push)"
  ],
  "recheck_combined_state": "failure",
  "recheck_failed_contexts": [
    "Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push)",
    "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)"
  ],
  "sha": "9981a5099a61836c296b82947ead0721affbf4c5"
}

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 `9981a5099a` Commit: <https://git.moleculesai.app/molecule-ai/molecule-core/commit/9981a5099a61836c296b82947ead0721affbf4c5> 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 - **Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/78360/jobs/0) - Failing after 6s - **Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/78368/jobs/0) - Failing after 4m41s ## 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 Chat / detect-changes (push)", "state": "success" }, { "context": "Handlers Postgres Integration / detect-changes (push)", "state": "success" }, { "context": "E2E Staging Canvas (Playwright) / detect-changes (push)", "state": "success" }, { "context": "Lint curl status-code capture / Scan workflows for curl status-capture pollution (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": "Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (push)", "state": "success" }, { "context": "lint-required-workflows-docker-host-pinned / Lint docker-host pin on docker-touching workflows (push)", "state": "success" }, { "context": "Secret scan / Scan diff for credential-shaped strings (push)", "state": "success" }, { "context": "CI / Shellcheck (E2E scripts) (push)", "state": "success" }, { "context": "E2E API Smoke Test / E2E API Smoke Test (push)", "state": "success" }, { "context": "E2E Chat / E2E Chat (push)", "state": "success" }, { "context": "lint-continue-on-error-tracking / lint-continue-on-error-tracking (push)", "state": "success" }, { "context": "Lint workflow YAML (Gitea-1.22.6-hostile shapes) / Lint workflow YAML for Gitea-1.22.6-hostile shapes (push)", "state": "success" }, { "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)", "state": "success" }, { "context": "publish-workspace-server-image / build-and-push (push)", "state": "success" }, { "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)", "state": "success" }, { "context": "CI / Platform (Go) (push)", "state": "success" }, { "context": "CI / Canvas (Next.js) (push)", "state": "success" }, { "context": "CI / Canvas Deploy Reminder (push)", "state": "success" }, { "context": "CI / all-required (push)", "state": "success" }, { "context": "publish-workspace-server-image / Production auto-deploy (push)", "state": "success" }, { "context": "gate-check-v3 / gate-check (push)", "state": "success" }, { "context": "Sweep stale Cloudflare DNS records / Sweep CF orphans (push)", "state": "success" }, { "context": "ci-required-drift / drift (push)", "state": "success" }, { "context": "Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push)", "state": "failure" }, { "context": "Sweep stale Cloudflare Tunnels / Sweep CF tunnels (push)", "state": "success" }, { "context": "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)", "state": "pending" }, { "context": "Sweep stale e2e-* orgs (staging) / Sweep e2e orgs (push)", "state": "success" }, { "context": "Continuous synthetic E2E (staging) / Synthetic E2E against staging (push)", "state": "pending" }, { "context": "main-red-watchdog / watchdog (push)", "state": "pending" } ], "branch": "main", "combined_state": "failure", "failed_contexts": [ "Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push)" ], "recheck_combined_state": "failure", "recheck_failed_contexts": [ "Sweep stale AWS Secrets Manager secrets / Sweep AWS Secrets Manager (push)", "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)" ], "sha": "9981a5099a61836c296b82947ead0721affbf4c5" } ``` _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 22:07:26 +00:00
agent-researcher commented 2026-05-26 09:01:10 +00:00
Member
Copy Link
Copy Source

RCA — root cause

#1656 is not a product-code regression; it is an ops credential/janitor failure plus the broader staging smoke cluster. The immediate red context failed after 6s in Sweep stale AWS Secrets Manager secrets, which matches the workflow's required-secret preflight rather than the AWS deletion loop. The later staging-smoke red shares the same staging CP/provider harness seen in #1665/#1663/#1659.

Evidence

  • Issue debug — product contexts (CI / Platform, Canvas, CI / all-required, build-and-push, production auto-deploy) were success; failed contexts were AWS Secrets sweep and staging smoke.
  • .gitea/workflows/sweep-aws-secrets.yml:72-83 — the janitor requires dedicated AWS janitor keys plus prod and staging CP admin tokens.
  • .gitea/workflows/sweep-aws-secrets.yml:87-110 — scheduled runs exit 1 immediately when any required secret is absent, matching the 6s failure.
  • scripts/ops/sweep-aws-secrets.sh:91-98 — script also hard-requires CP_ADMIN_API_TOKEN, CP_STAGING_ADMIN_API_TOKEN, AWS keys, and aws CLI before any sweep logic.
  • scripts/ops/sweep-aws-secrets.sh:109-118 — successful sweep depends on both prod and staging CP admin APIs to build the live-org set before AWS deletion planning.

Suggested fix

Route to CI/ops secret provisioning and janitor hardening. First verify which of AWS_SECRETS_JANITOR_ACCESS_KEY_ID, AWS_SECRETS_JANITOR_SECRET_ACCESS_KEY, CP_ADMIN_API_TOKEN, or CP_STAGING_ADMIN_API_TOKEN was empty/rotated in run 78360. If all are present, next suspect is AWS janitor IAM scope or CP admin API failure. Keep this separate from product rollback; the durable fix is a visible ops-secret health check plus raw first-failure excerpts in main-red watchdog for scheduled janitors.

Confidence

Medium-high — 6s runtime plus workflow preflight lines strongly indicate missing/invalid required ops credentials, though raw logs are needed to name the exact variable.

## RCA — root cause `#1656` is not a product-code regression; it is an ops credential/janitor failure plus the broader staging smoke cluster. The immediate red context failed after 6s in `Sweep stale AWS Secrets Manager secrets`, which matches the workflow's required-secret preflight rather than the AWS deletion loop. The later staging-smoke red shares the same staging CP/provider harness seen in #1665/#1663/#1659. ## Evidence - Issue debug — product contexts (`CI / Platform`, Canvas, `CI / all-required`, build-and-push, production auto-deploy) were `success`; failed contexts were AWS Secrets sweep and staging smoke. - `.gitea/workflows/sweep-aws-secrets.yml:72-83` — the janitor requires dedicated AWS janitor keys plus prod and staging CP admin tokens. - `.gitea/workflows/sweep-aws-secrets.yml:87-110` — scheduled runs exit 1 immediately when any required secret is absent, matching the 6s failure. - `scripts/ops/sweep-aws-secrets.sh:91-98` — script also hard-requires `CP_ADMIN_API_TOKEN`, `CP_STAGING_ADMIN_API_TOKEN`, AWS keys, and `aws` CLI before any sweep logic. - `scripts/ops/sweep-aws-secrets.sh:109-118` — successful sweep depends on both prod and staging CP admin APIs to build the live-org set before AWS deletion planning. ## Suggested fix Route to CI/ops secret provisioning and janitor hardening. First verify which of `AWS_SECRETS_JANITOR_ACCESS_KEY_ID`, `AWS_SECRETS_JANITOR_SECRET_ACCESS_KEY`, `CP_ADMIN_API_TOKEN`, or `CP_STAGING_ADMIN_API_TOKEN` was empty/rotated in run `78360`. If all are present, next suspect is AWS janitor IAM scope or CP admin API failure. Keep this separate from product rollback; the durable fix is a visible ops-secret health check plus raw first-failure excerpts in main-red watchdog for scheduled janitors. ## Confidence Medium-high — 6s runtime plus workflow preflight lines strongly indicate missing/invalid required ops credentials, though raw logs are needed to name the exact variable.
gitea-actions bot commented 2026-05-26 16:05:58 +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:58 +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#1656
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?