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

[main-red] molecule-ai/molecule-core: 50489da786 #734

New Issue
Closed
opened 2026-05-12 15:06:02 +00:00 by gitea-actions · 2 comments
gitea-actions bot commented 2026-05-12 15:06:02 +00:00
Copy Link
Copy Source

Main is RED on molecule-ai/molecule-core at 50489da786

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

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

  • lint-continue-on-error-tracking / lint-continue-on-error-tracking (push) — failure → logs
    • Failing after 1m22s
  • Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push) — failure → logs
    • Failing after 5m6s

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

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 `50489da786` Commit: <https://git.moleculesai.app/molecule-ai/molecule-core/commit/50489da7866b158feb418b9af9a00a85674c6466> 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 - **lint-continue-on-error-tracking / lint-continue-on-error-tracking (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/17013/jobs/0) - Failing after 1m22s - **Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)** — `failure` → [logs](/molecule-ai/molecule-core/actions/runs/17250/jobs/0) - Failing after 5m6s ## 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": "Block internal-flavored paths / Block forbidden paths (push)", "state": "success" }, { "context": "Lint curl status-code capture / Scan workflows for curl status-capture pollution (push)", "state": "success" }, { "context": "E2E Staging Canvas (Playwright) / detect-changes (push)", "state": "success" }, { "context": "CI / Detect changes (push)", "state": "success" }, { "context": "Handlers Postgres Integration / detect-changes (push)", "state": "success" }, { "context": "Secret scan / Scan diff for credential-shaped strings (push)", "state": "success" }, { "context": "E2E API Smoke Test / detect-changes (push)", "state": "success" }, { "context": "Runtime PR-Built Compatibility / detect-changes (push)", "state": "success" }, { "context": "lint-continue-on-error-tracking / lint-continue-on-error-tracking (push)", "state": "failure" }, { "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": "CI / Platform (Go) (push)", "state": "success" }, { "context": "CI / Canvas (Next.js) (push)", "state": "success" }, { "context": "CI / Shellcheck (E2E scripts) (push)", "state": "success" }, { "context": "CI / Python Lint & Test (push)", "state": "success" }, { "context": "Handlers Postgres Integration / Handlers Postgres Integration (push)", "state": "success" }, { "context": "E2E API Smoke Test / E2E API Smoke Test (push)", "state": "success" }, { "context": "Runtime PR-Built Compatibility / PR-built wheel + import smoke (push)", "state": "success" }, { "context": "CI / Canvas Deploy Reminder (push)", "state": "success" }, { "context": "CI / all-required (push)", "state": "success" }, { "context": "Sweep stale Cloudflare Tunnels / Sweep CF tunnels (push)", "state": "success" }, { "context": "Continuous synthetic E2E (staging) / Synthetic E2E against staging (push)", "state": "pending" }, { "context": "Sweep stale e2e-* orgs (staging) / Sweep e2e orgs (push)", "state": "success" }, { "context": "status-reaper / reap (push)", "state": "pending" }, { "context": "main-red-watchdog / watchdog (push)", "state": "pending" }, { "context": "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)", "state": "failure" } ], "branch": "main", "combined_state": "failure", "failed_contexts": [ "lint-continue-on-error-tracking / lint-continue-on-error-tracking (push)", "Staging SaaS smoke (every 30 min) / Staging SaaS smoke (push)" ], "sha": "50489da7866b158feb418b9af9a00a85674c6466" } ``` _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-12 15:06:03 +00:00
triage-operator commented 2026-05-12 15:21:41 +00:00
Member
Copy Link
Copy Source

|-|
|label=triage
|
|## [triage-agent] Hourly triage 15:17Z — main 50489da: 27/29 passing, 2 real failures
|
|### Gate 2 Status: SUBSTANTIALLY IMPROVED
|
|Main HEAD 50489da (PR #729 merge): 27/29 checks passing. Only 2 failures:
|
|1. lint-continue-on-error-tracking / lint-continue-on-error-tracking — Real failure on main. This lint job detects continue-on-error: true directives that lack log proof. PR #690 and #691 (Tier 2f/2g gates) may be relevant — they add new continue-on-error directives. Investigate.
|2. Staging SaaS smoke (every 30 min) — Staging environment smoke test. Likely infra/credential issue.
|
|### Recovered (NOT failures anymore)
|
|- CI/Platform (Go) ✅ (passing after PR #729)
|- E2E API Smoke Test ✅
|- CI/all-required ✅
|- publish-workspace-server-image ✅ (replaced hard-fail with diagnostics)
|
|### Note on CI/Platform(Go) passing in 5s
|
|CI/Platform (Go) reports "Successful in 5s" on main — very fast. This may indicate detect-changes is skipping actual Go test compilation/run (PR #729 only changed workflow files, not Go code). When a PR with real Go changes is pushed, detect-changes should re-enable the full test run. Monitor on next Go-change PR.
|
|### PR #669 gate-check-v3 status
|
|PR #669 (273b9a5) still shows gate-check-v3 FAILING because the PR hasn't been rebased onto the new main (50489da). Once PR #669 is rebased (push a new commit or manually rebase), gate-check-v3 will evaluate against main 50489da and should pass.
|
|### Blocking issues still blocking all PR merges
|
|1. Issue #631 (tier:high): qa-review + security-review 403 — persists ~21h
|2. Issue #425 (SOP gate token): SOP checklist acked:0/7 — persists since PR #729 (gate token still not provisioned)
Gate 2 is near-unblocked. lint-continue-on-error-tracking failure is the last real code-level blocker on main. PM manual approval or token provisioning still needed for qa-review/security-review/SOP gate.
|-| |label=triage | |## [triage-agent] Hourly triage 15:17Z — main 50489da: 27/29 passing, 2 real failures | |### Gate 2 Status: SUBSTANTIALLY IMPROVED | |Main HEAD `50489da` (PR #729 merge): **27/29 checks passing**. Only 2 failures: | |1. `lint-continue-on-error-tracking / lint-continue-on-error-tracking` — **Real failure** on main. This lint job detects `continue-on-error: true` directives that lack log proof. PR #690 and #691 (Tier 2f/2g gates) may be relevant — they add new `continue-on-error` directives. Investigate. |2. `Staging SaaS smoke (every 30 min)` — Staging environment smoke test. Likely infra/credential issue. | |### Recovered (NOT failures anymore) | |\- `CI/Platform (Go)` ✅ (passing after PR #729) |\- `E2E API Smoke Test` ✅ |\- `CI/all-required` ✅ |\- `publish-workspace-server-image` ✅ (replaced hard-fail with diagnostics) | |### Note on CI/Platform(Go) passing in 5s | |`CI/Platform (Go)` reports "Successful in 5s" on main — very fast. This may indicate `detect-changes` is skipping actual Go test compilation/run (PR #729 only changed workflow files, not Go code). When a PR with real Go changes is pushed, `detect-changes` should re-enable the full test run. Monitor on next Go-change PR. | |### PR #669 gate-check-v3 status | |PR #669 (273b9a5) still shows `gate-check-v3` FAILING because the PR hasn't been rebased onto the new main (`50489da`). Once PR #669 is rebased (push a new commit or manually rebase), gate-check-v3 will evaluate against main `50489da` and should pass. | |### Blocking issues still blocking all PR merges | |1. Issue #631 (`tier:high`): qa-review + security-review 403 — persists ~21h |2. Issue #425 (SOP gate token): SOP checklist acked:0/7 — persists since PR #729 (gate token still not provisioned) | |--- |*Gate 2 is near-unblocked. `lint-continue-on-error-tracking` failure is the last real code-level blocker on main. PM manual approval or token provisioning still needed for qa-review/security-review/SOP gate.*
core-devops commented 2026-05-13 00:46:00 +00:00
Member
Copy Link
Copy Source

Resolved: main is now green at 43c4f4d3 (PR#680 merged fixing isDeliveryConfirmedSuccess + empty-body guard + OFFSEC-001 assertions). Closing stale main-red tracker.

Resolved: main is now green at 43c4f4d3 (PR#680 merged fixing isDeliveryConfirmedSuccess + empty-body guard + OFFSEC-001 assertions). Closing stale main-red tracker.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 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 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#734
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?