bug: Forgejo pending CI checks open broken live logs #689

New issue

Closed

opened 2026-05-09 16:52:01 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-05-09 16:52:01 +00:00

Owner

Prerequisites

I have searched existing issues
I have updated to the latest version

Neovim version

current local development checkout

Operating system

Linux

Description

Pressing <CR> on an in-progress Forgejo PR CI check opens tea actions runs logs --follow. On this Forgejo instance, tea actions runs logs requests unsupported Actions job endpoints and fails with a raw 404, for example:

Following logs for job 1 (press Ctrl+C to stop)...
---
Error: failed to get job: unknown API error: 404
Request: '/api/v1/repos/barrettruth/forge.nvim/actions/jobs/1' with 'GET' method and '404 page not found
' body

This reproduces outside Neovim against a completed successful run too, so it is not only a queued-run or runner-outage state. forge.nvim already has a Forgejo web-log fallback path for run/check logs; pending PR checks should use that path instead of the broken live-tail command.

Steps to reproduce

Open :Forge pr ci on a Forgejo PR with a pending or in-progress check.
Press <CR> on the check entry.
Observe the terminal buffer fail through tea actions runs logs --follow with /actions/jobs/1 or /actions/runs/<id>/jobs 404.

Direct reproduction:

timeout 10 tea actions runs logs 2522 --follow --job 1 --repo barrettruth/forge.nvim

Health check

not applicable; reproduced through the backend command path

Forge CLI version

tea actions runs logs reproduces the failure on the current local tea installation

Minimal reproduction

vim.pack.add({
  'https://git.barrettruth.com/barrettruth/midnight.nvim',
  'https://github.com/tpope/vim-fugitive',
  'https://github.com/ibhagwan/fzf-lua',
  'https://git.barrettruth.com/barrettruth/forge.nvim',
})
vim.cmd.colorscheme('midnight')

## Prerequisites - [x] I have searched [existing issues](https://git.barrettruth.com/barrettruth/forge.nvim/issues) - [x] I have updated to the latest version ## Neovim version ```text current local development checkout ``` ## Operating system Linux ## Description Pressing `<CR>` on an in-progress Forgejo PR CI check opens `tea actions runs logs --follow`. On this Forgejo instance, `tea actions runs logs` requests unsupported Actions job endpoints and fails with a raw 404, for example: ```text Following logs for job 1 (press Ctrl+C to stop)... --- Error: failed to get job: unknown API error: 404 Request: '/api/v1/repos/barrettruth/forge.nvim/actions/jobs/1' with 'GET' method and '404 page not found ' body ``` This reproduces outside Neovim against a completed successful run too, so it is not only a queued-run or runner-outage state. forge.nvim already has a Forgejo web-log fallback path for run/check logs; pending PR checks should use that path instead of the broken live-tail command. ## Steps to reproduce 1. Open `:Forge pr ci` on a Forgejo PR with a pending or in-progress check. 2. Press `<CR>` on the check entry. 3. Observe the terminal buffer fail through `tea actions runs logs --follow` with `/actions/jobs/1` or `/actions/runs/<id>/jobs` 404. Direct reproduction: ```sh timeout 10 tea actions runs logs 2522 --follow --job 1 --repo barrettruth/forge.nvim ``` ## Health check ```text not applicable; reproduced through the backend command path ``` ## Forge CLI version ```text tea actions runs logs reproduces the failure on the current local tea installation ``` ## Minimal reproduction ```lua vim.pack.add({ 'https://git.barrettruth.com/barrettruth/midnight.nvim', 'https://github.com/tpope/vim-fugitive', 'https://github.com/ibhagwan/fzf-lua', 'https://git.barrettruth.com/barrettruth/forge.nvim', }) vim.cmd.colorscheme('midnight') ```

barrettruth added the

bug

label

2026-05-09 16:52:01 +00:00

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

2026-05-09 16:54:01 +00:00

Fix Forgejo pending CI log opening #690

barrettruth commented

2026-05-09 17:07:28 +00:00

Author

Owner

Upstream check:

Gitea documents repository Actions job/log endpoints and tea actions runs logs calls those endpoints.
Current Forgejo v15 swagger on git.barrettruth.com and Codeberg only exposes repository Actions run endpoints, not the job/log endpoints.
Forgejo already tracks first-class Actions job/log API support in https://codeberg.org/forgejo/forgejo/issues/11859. A duplicate report is not needed.

PR #690 now treats this as a Forgejo capability gap plus a queued-job lifecycle case: no tea actions runs logs --follow, fallback to the web-log buffer path, and a successful "logs are not available yet" placeholder while the runner has not produced job logs.

Upstream check: - Gitea documents repository Actions job/log endpoints and `tea actions runs logs` calls those endpoints. - Current Forgejo v15 swagger on git.barrettruth.com and Codeberg only exposes repository Actions run endpoints, not the job/log endpoints. - Forgejo already tracks first-class Actions job/log API support in https://codeberg.org/forgejo/forgejo/issues/11859. A duplicate report is not needed. PR #690 now treats this as a Forgejo capability gap plus a queued-job lifecycle case: no `tea actions runs logs --follow`, fallback to the web-log buffer path, and a successful "logs are not available yet" placeholder while the runner has not produced job logs.

barrettruth closed this issue

2026-05-09 17:13:06 +00:00

barrettruth referenced this issue from a commit

2026-05-09 17:13:08 +00:00

Fix Forgejo pending CI log opening (#690)