forgejo-actions-logs bridge 404s against Forgejo 15: port to the UI log-cursor route + add a ward verb #476

New issue

Closed

opened 2026-07-12 06:20:01 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-07-12 06:20:01 +00:00

Owner

The agentic_os.forgejo_actions_logs bridge (and .ward/forgejo-actions-logs.sh) resolves ids fine but its final fetch hits GET /api/v1/repos/{o}/{r}/actions/runs/{run_id}/jobs/{job_id}/attempt/{n}/logs, which 404s on the current deployment (Forgejo 15.0.2) even for fresh, successful runs - verified against runs 1055/1063 (aos) and 1823 (ward).

Working route found during the 2026-07-11 stability session: POST {owner}/{repo}/actions/runs/{run_index}/jobs/{job_index}/attempt/{attempt} with body {"logCursors":[{"step":N,"cursor":null,"expanded":true}]} returns logs.stepsLog[].lines[]. The /attempt/{n} segment is REQUIRED - without it the handler resolves attempt 0 and errors "task ... attempt 0: resource does not exist".

Also: there is no ward.yaml verb for the bridge, so an agent needing CI logs has to hand-roll HTTP. Add ward exec forgejo-actions-logs -- <owner> <repo> <run_index> <job_index> [attempt] alongside the port.

The `agentic_os.forgejo_actions_logs` bridge (and `.ward/forgejo-actions-logs.sh`) resolves ids fine but its final fetch hits `GET /api/v1/repos/{o}/{r}/actions/runs/{run_id}/jobs/{job_id}/attempt/{n}/logs`, which 404s on the current deployment (Forgejo 15.0.2) even for fresh, successful runs - verified against runs 1055/1063 (aos) and 1823 (ward). Working route found during the 2026-07-11 stability session: `POST {owner}/{repo}/actions/runs/{run_index}/jobs/{job_index}/attempt/{attempt}` with body `{"logCursors":[{"step":N,"cursor":null,"expanded":true}]}` returns `logs.stepsLog[].lines[]`. The `/attempt/{n}` segment is REQUIRED - without it the handler resolves attempt 0 and errors "task ... attempt 0: resource does not exist". Also: there is no ward.yaml verb for the bridge, so an agent needing CI logs has to hand-roll HTTP. Add `ward exec forgejo-actions-logs -- <owner> <repo> <run_index> <job_index> [attempt]` alongside the port.

coilysiren referenced this issue from a commit

2026-07-12 06:27:33 +00:00

fix(forgejo-logs): speak the UI log-cursor route + add a ward verb (closes #476)

coilysiren referenced this issue from a pull request that will close it,

2026-07-12 06:27:45 +00:00

fix(forgejo-logs): speak the UI log-cursor route + add a ward verb #478

coilysiren closed this issue

2026-07-12 06:39:12 +00:00