Skip to content

ci-health: main CI is red on WasmAgent/symkernel (workflow "CI") #271

Description

@telleroutlook

The most recent completed CI run on main in WasmAgent/symkernel concluded in failure.

A red main blocks every subsequent PR (their CI runs against a broken base) and must be repaired before other work can land. Inspect the failing run, reproduce locally, and push a fix to main.

Failing run: https://github.com/WasmAgent/symkernel/actions/runs/30504092814

Acceptance criteria: the next completed CI run on main concludes success.

Files

  • ""/tmp/tmp.ufhVOKX3Uq"/wasmagent-js"/packages/cloudflare-worker/src/index.ts
  • ""/tmp/tmp.ufhVOKX3Uq"/wasmagent-js"/packages/cloudflare-worker/src/index.test.ts
  • ""/tmp/tmp.ufhVOKX3Uq"/wasmagent-js"/packages/model-local/src/presets.test.ts
  • ""/tmp/tmp.ufhVOKX3Uq"/wasmagent-js"/examples/owasp-demo/scenarios.ts
  • ""/tmp/tmp.ufhVOKX3Uq"/wasmagent-js"/examples/multi-agent-replay/index.ts
  • ""/tmp/tmp.ufhVOKX3Uq"/wasmagent-js"/docs/.vitepress/config.ts

Acceptance criteria

  • Command go build ./... passes
  • The specific fix described above is implemented in the smallest number of files required.
  • No unrelated files touched (git status --short output limited to the intended change).

Metadata

Metadata

Assignees

No one assigned

    Labels

    claudeBot-managed issuepatrolFiled by patrol daemonpatrol-fixPatrol-filed fix issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions