molecule-ai/molecule-core
44
0
Fork 2
Code Issues 134 Pull Requests 156 Actions Packages Projects Releases Wiki Activity

[main-red] molecule-ai/molecule-core: c8b06c1367 #583

New Issue
Closed
opened 2026-05-11 22:10:40 +00:00 by gitea-actions · 1 comment
gitea-actions bot commented 2026-05-11 22:10:40 +00:00
Copy Link
Copy Source

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

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

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

(Combined state reported failure/error but no per-context entries were in a red state. This usually means a CI emitter set combined-status directly without a per-context status. Check the most recent workflow run for main and trace from there.)

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 / Canvas Deploy Reminder (push)",
      "state": null
    },
    {
      "context": "CI / all-required (push)",
      "state": null
    },
    {
      "context": "Block internal-flavored paths / Block forbidden paths (push)",
      "state": null
    },
    {
      "context": "CI / Detect changes (push)",
      "state": null
    },
    {
      "context": "Lint curl status-code capture / Scan workflows for curl status-capture pollution (push)",
      "state": null
    },
    {
      "context": "Secret scan / Scan diff for credential-shaped strings (push)",
      "state": null
    },
    {
      "context": "E2E API Smoke Test / detect-changes (push)",
      "state": null
    },
    {
      "context": "publish-workspace-server-image / build-and-push (push)",
      "state": null
    },
    {
      "context": "E2E Staging Canvas (Playwright) / detect-changes (push)",
      "state": null
    },
    {
      "context": "Handlers Postgres Integration / detect-changes (push)",
      "state": null
    },
    {
      "context": "Runtime PR-Built Compatibility / detect-changes (push)",
      "state": null
    },
    {
      "context": "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)",
      "state": null
    },
    {
      "context": "Continuous synthetic E2E (staging) / Synthetic E2E against staging (push)",
      "state": null
    },
    {
      "context": "Sweep stale e2e-* orgs (staging) / Sweep e2e orgs (push)",
      "state": null
    },
    {
      "context": "CI / Platform (Go) (push)",
      "state": null
    },
    {
      "context": "CI / Shellcheck (E2E scripts) (push)",
      "state": null
    },
    {
      "context": "CI / Canvas (Next.js) (push)",
      "state": null
    },
    {
      "context": "main-red-watchdog / watchdog (push)",
      "state": null
    },
    {
      "context": "CI / Python Lint & Test (push)",
      "state": null
    },
    {
      "context": "E2E API Smoke Test / E2E API Smoke Test (push)",
      "state": null
    },
    {
      "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)",
      "state": null
    },
    {
      "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)",
      "state": null
    },
    {
      "context": "Runtime PR-Built Compatibility / PR-built wheel + import smoke (push)",
      "state": null
    }
  ],
  "branch": "main",
  "combined_state": "failure",
  "failed_contexts": [],
  "sha": "c8b06c1367adec9db91b43f7c4a27bba2e451288"
}

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 `c8b06c1367` Commit: <https://git.moleculesai.app/molecule-ai/molecule-core/commit/c8b06c1367adec9db91b43f7c4a27bba2e451288> 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 _(Combined state reported `failure`/`error` but no per-context entries were in a red state. This usually means a CI emitter set combined-status directly without a per-context status. Check the most recent workflow run for `main` and trace from there.)_ ## 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 / Canvas Deploy Reminder (push)", "state": null }, { "context": "CI / all-required (push)", "state": null }, { "context": "Block internal-flavored paths / Block forbidden paths (push)", "state": null }, { "context": "CI / Detect changes (push)", "state": null }, { "context": "Lint curl status-code capture / Scan workflows for curl status-capture pollution (push)", "state": null }, { "context": "Secret scan / Scan diff for credential-shaped strings (push)", "state": null }, { "context": "E2E API Smoke Test / detect-changes (push)", "state": null }, { "context": "publish-workspace-server-image / build-and-push (push)", "state": null }, { "context": "E2E Staging Canvas (Playwright) / detect-changes (push)", "state": null }, { "context": "Handlers Postgres Integration / detect-changes (push)", "state": null }, { "context": "Runtime PR-Built Compatibility / detect-changes (push)", "state": null }, { "context": "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)", "state": null }, { "context": "Continuous synthetic E2E (staging) / Synthetic E2E against staging (push)", "state": null }, { "context": "Sweep stale e2e-* orgs (staging) / Sweep e2e orgs (push)", "state": null }, { "context": "CI / Platform (Go) (push)", "state": null }, { "context": "CI / Shellcheck (E2E scripts) (push)", "state": null }, { "context": "CI / Canvas (Next.js) (push)", "state": null }, { "context": "main-red-watchdog / watchdog (push)", "state": null }, { "context": "CI / Python Lint & Test (push)", "state": null }, { "context": "E2E API Smoke Test / E2E API Smoke Test (push)", "state": null }, { "context": "E2E Staging Canvas (Playwright) / Canvas tabs E2E (push)", "state": null }, { "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)", "state": null }, { "context": "Runtime PR-Built Compatibility / PR-built wheel + import smoke (push)", "state": null } ], "branch": "main", "combined_state": "failure", "failed_contexts": [], "sha": "c8b06c1367adec9db91b43f7c4a27bba2e451288" } ``` _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-11 22:10:42 +00:00
hongming-pc2 commented 2026-05-11 22:33:26 +00:00
Owner
Copy Link
Copy Source

Mostly #504-class op-noise; one footnote worth a quick look. Recommend close as dup of #561 once status-reaper #589 merges.

Per-context reds on c8b06c1367ad (= #572 merge):

Context Class Tracking
publish-workspace-server-image / build-and-push (push) real-but-known-defect mc#576 (runner-pool docker.sock); #585 diagnostic probes in flight
Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push) #504 op-noise (schedule workflow with (push) suffix) #424
Sweep stale Cloudflare DNS records / Sweep CF orphans (push) #504 op-noise #504 / #589 status-reaper will compensate
gate-check-v3 / gate-check (push) check below ↓ #564 supposedly fixed; worth verifying on a fresh run

Footnote — gate-check-v3 on this commit: #564 (merged 21:09Z) removed the elif ci_state == "failure": verdict = "CI_FAIL" self-loop, leaving failing_required as the sole driver. Staging-SaaS-smoke / Sweep-CF-orphans aren't in branch_protections.status_check_contexts (not required), so they shouldn't drive failing_required to non-empty. Two possibilities for why gate-check-v3 still posted red on c8b06c1367:

  1. The run was on a pr_data.base.sha snapshot from before #564 merged (verify the run's checkout SHA).
  2. gate-check-v3 has a separate failure mode (e.g. the residual ci_state == "pending" self-ref I flagged as a non-blocking note on #564's review 1489 — same class of bug, just on the pending path).
  3. Or some legitimately-required check WAS red. Worth a 30-second peek at the run's emitted failing_required list.

If it's (2), that's the fast-follow #564 review flagged. If it's (1), it self-resolves on the next push. As of current main HEAD 3ba138d37e84, gate-check-v3 is NOT in the red list — so it didn't reproduce on the subsequent commit. Likely (1), but worth a glance.

Recommendation: close this as dup of #561 (live main-combined-status thread). Once status-reaper #589 (Five-Axis APPROVE'd 1548, awaiting merge) lands AND mc#576 fixes the publish-ws-server real defect, main's combined status flips to green and the watchdog stops filing these. Not reverting anything (feedback_fix_root_not_symptom).

— hongming-pc2

## Mostly #504-class op-noise; one footnote worth a quick look. Recommend close as dup of #561 once status-reaper #589 merges. Per-context reds on `c8b06c1367ad` (= #572 merge): | Context | Class | Tracking | |---|---|---| | `publish-workspace-server-image / build-and-push (push)` | real-but-known-defect | **mc#576** (runner-pool docker.sock); #585 diagnostic probes in flight | | `Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)` | #504 op-noise (schedule workflow with `(push)` suffix) | #424 | | `Sweep stale Cloudflare DNS records / Sweep CF orphans (push)` | #504 op-noise | #504 / **#589 status-reaper will compensate** | | `gate-check-v3 / gate-check (push)` | check below ↓ | #564 supposedly fixed; worth verifying on a fresh run | **Footnote — gate-check-v3 on this commit**: #564 (merged 21:09Z) removed the `elif ci_state == "failure": verdict = "CI_FAIL"` self-loop, leaving `failing_required` as the sole driver. `Staging-SaaS-smoke` / `Sweep-CF-orphans` aren't in `branch_protections.status_check_contexts` (not required), so they shouldn't drive `failing_required` to non-empty. Two possibilities for why gate-check-v3 still posted red on `c8b06c1367`: 1. The run was on a `pr_data.base.sha` snapshot from *before* #564 merged (verify the run's checkout SHA). 2. `gate-check-v3` has a *separate* failure mode (e.g. the residual `ci_state == "pending"` self-ref I flagged as a non-blocking note on #564's review 1489 — same class of bug, just on the pending path). 3. Or some legitimately-required check WAS red. Worth a 30-second peek at the run's emitted `failing_required` list. If it's (2), that's the fast-follow #564 review flagged. If it's (1), it self-resolves on the next push. **As of current `main` HEAD `3ba138d37e84`, `gate-check-v3` is NOT in the red list** — so it didn't reproduce on the subsequent commit. Likely (1), but worth a glance. **Recommendation**: close this as dup of #561 (live `main`-combined-status thread). Once status-reaper **#589** (Five-Axis APPROVE'd 1548, awaiting merge) lands AND mc#576 fixes the publish-ws-server real defect, `main`'s combined status flips to green and the watchdog stops filing these. Not reverting anything (`feedback_fix_root_not_symptom`). — hongming-pc2
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 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
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 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-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 plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot 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#583
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?