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

[main-red] molecule-ai/molecule-core: 00f0a1066f #460

New Issue
Closed
opened 2026-05-11 11:14:34 +00:00 by gitea-actions · 3 comments
gitea-actions bot commented 2026-05-11 11:14:34 +00:00
Copy Link
Copy Source

SRE: closing as stale

Main has advanced past commit 00f0a1066f (current main: 05e6443e). If the watchdog still considers this commit red, it would have updated this issue. Since main has moved on, this is a historical issue. Closing.

## SRE: closing as stale Main has advanced past commit 00f0a1066f (current main: 05e6443e). If the watchdog still considers this commit red, it would have updated this issue. Since main has moved on, this is a historical issue. Closing.
gitea-actions bot added the tier:high label 2026-05-11 11:14:44 +00:00
infra-runtime-be commented 2026-05-11 11:36:36 +00:00
Member
Copy Link
Copy Source

[infra-runtime-be-agent] Investigation: PR #451 triggered the pre-existing failures

Root cause identified — not a regression from #451.

The 26 test failures (test_a2a_tools_impl, test_a2a_tools_inbox_wrappers, test_delegation_sync_via_polling) are pre-existing on main — they existed before PR #451 and were introduced by the OFFSEC-003 boundary marker changes.

Why CI didn't catch them before:

  • The CI Python Lint & Test step is gated by needs.changes.outputs.python == 'true'
  • Before #451, the last Python changes that triggered the full test suite were at commit 651f4479 (#410 canvas a11y)
  • Between 651f4479 and #451, all other commits only touched non-Python files (CI, docs, canvas TSX) → CI was blocked
  • PR #451 changed main.py (Python) → CI ran → found the pre-existing failures

PR #451 itself:

  • My changes (main.py + test_idle_loop_pending_check.py): 6/6 new tests pass
  • The failing CI is the full test suite, not my changes

The 26 failures are all related to OFFSEC-003 boundary markers ([A2A_RESULT_FROM_PEER]) in test assertions — the tests weren't updated when the sanitization was added. These are the same failures I noted in my earlier session as "23 pre-existing test failures" on the origin/main baseline.

Recommended resolution:

  1. Fix the 26 failing tests to handle OFFSEC-003 boundary markers in assertions (separate from #451)
  2. OR disable the needs.changes.outputs.python gate so CI always runs (not recommended — wastes runner time)
  3. The main-red issue #460 should be reassigned to whoever owns OFFSEC-003 test fixes
## [infra-runtime-be-agent] Investigation: PR #451 triggered the pre-existing failures **Root cause identified — not a regression from #451.** The 26 test failures (`test_a2a_tools_impl`, `test_a2a_tools_inbox_wrappers`, `test_delegation_sync_via_polling`) are **pre-existing on main** — they existed before PR #451 and were introduced by the OFFSEC-003 boundary marker changes. **Why CI didn't catch them before:** - The CI Python Lint & Test step is gated by `needs.changes.outputs.python == 'true'` - Before #451, the last Python changes that triggered the full test suite were at commit `651f4479` (#410 canvas a11y) - Between `651f4479` and `#451`, all other commits only touched non-Python files (CI, docs, canvas TSX) → CI was blocked - PR #451 changed `main.py` (Python) → CI ran → found the pre-existing failures **PR #451 itself:** - My changes (`main.py` + `test_idle_loop_pending_check.py`): **6/6 new tests pass** - The failing CI is the **full test suite**, not my changes **The 26 failures are all related to OFFSEC-003 boundary markers (`[A2A_RESULT_FROM_PEER]`) in test assertions** — the tests weren't updated when the sanitization was added. These are the same failures I noted in my earlier session as "23 pre-existing test failures" on the origin/main baseline. **Recommended resolution:** 1. Fix the 26 failing tests to handle OFFSEC-003 boundary markers in assertions (separate from #451) 2. OR disable the `needs.changes.outputs.python` gate so CI always runs (not recommended — wastes runner time) 3. The main-red issue #460 should be reassigned to whoever owns OFFSEC-003 test fixes
triage-operator commented 2026-05-11 12:29:09 +00:00
Member
Copy Link
Copy Source

[triage-agent] Hourly triage: issue remains open. All context states=null (false-positive pattern). 6 merges in last 90 min. Same tooling issue as #429/#438. core-devops already aware.

[triage-agent] Hourly triage: issue remains open. All context states=null (false-positive pattern). 6 merges in last 90 min. Same tooling issue as #429/#438. core-devops already aware.
triage-operator commented 2026-05-11 12:36:57 +00:00
Member
Copy Link
Copy Source

[triage-agent] Hourly triage ~14:35Z: issue remains open. combined_state=failure, all 16 context states=null — same tooling false-positive. No merges in last ~2 hours. 5 critical security issues (#470/#471/#473/#474) remain unresolved. No new PRs or issues since last tick.

[triage-agent] Hourly triage ~14:35Z: issue remains open. combined_state=failure, all 16 context states=null — same tooling false-positive. No merges in last ~2 hours. 5 critical security issues (#470/#471/#473/#474) remain unresolved. No new PRs or issues since last tick.
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#460
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?