dsh-plugins/dsh-gitea

Watch

Fork 0

fix(issues): gitea_issue_list silently hides everything past 20 rows #2

New issue

Closed

opened 2026-10-23 17:17:52 +00:00 by dsh · 1 comment

dsh commented

2026-10-23 17:17:52 +00:00

Owner

Symptom

gitea_issue_list never returns more than 20 rows, whatever limit is passed. pvlb-infra/vps-setup has 28 issues (state=all); the tool shows 20 and the model has no idea the rest exist.

Reproduced 2026-10-23:

call	tool output	direct REST API
`limit:50, page:1`	20 rows	28 rows
`limit:100, page:1`	20 rows	28 rows
`limit:50, page:2`	`OK` (empty)	0 rows (offset 50 — correct)
`limit:20, page:2`	8 rows	8 rows

Root cause

The request is fine; the formatter cuts the response:

// lib/handlers/formatters.js:205
const lines = data.slice(0, 20).map((item) => { ... })

The tool result the model sees is built from this text, so 8 issues vanish even though wrap() returned them.

Fix

Render every row the API returned (the page size is already controlled by the caller's limit/page), or cap deliberately at 100 with an explicit footer such as … and 8 more — call again with page: 2. Silent truncation is the bug; a visible truncation would be acceptable.

Acceptance

28 issues + limit:50 → all 28 rows (or 20 + "8 more" footer).
limit:5 still returns exactly 5.
The formatter never drops rows without saying so.

## Symptom `gitea_issue_list` never returns more than **20 rows**, whatever `limit` is passed. `pvlb-infra/vps-setup` has 28 issues (`state=all`); the tool shows 20 and the model has no idea the rest exist. Reproduced 2026-10-23: | call | tool output | direct REST API | |---|---|---| | `limit:50, page:1` | 20 rows | 28 rows | | `limit:100, page:1` | 20 rows | 28 rows | | `limit:50, page:2` | `OK` (empty) | 0 rows (offset 50 — correct) | | `limit:20, page:2` | 8 rows | 8 rows | ## Root cause The request is fine; the **formatter** cuts the response: ```js // lib/handlers/formatters.js:205 const lines = data.slice(0, 20).map((item) => { ... }) ``` The tool result the model sees is built from this text, so 8 issues vanish even though `wrap()` returned them. ## Fix Render every row the API returned (the page size is already controlled by the caller's `limit`/`page`), or cap deliberately at 100 with an **explicit** footer such as `… and 8 more — call again with page: 2`. Silent truncation is the bug; a visible truncation would be acceptable. ## Acceptance - [ ] 28 issues + `limit:50` → all 28 rows (or 20 + "8 more" footer). - [ ] `limit:5` still returns exactly 5. - [ ] The formatter never drops rows without saying so.

dsh referenced this issue

2026-10-23 17:17:53 +00:00

fix(tools): empty and unrecognised results render as a bare OK #5

dsh added the

type/bug

area/forgejo

priority/now

labels

2026-10-23 17:18:02 +00:00

dsh referenced this issue

2026-10-23 17:18:08 +00:00

Tool bugs seen from issue-tracker work (2026-10-23): wiki get, repo contents, issue pagination, empty responses, label assignment #1

dsh referenced this issue

2026-10-23 17:33:35 +00:00

feat(labels): gitea_labels list hides numeric ids, so action:set cannot use its own output #7

dsh referenced this issue from a commit

2026-10-23 18:05:07 +00:00

fix(tools): render complete lists and never print a bare OK

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

2026-10-23 18:05:11 +00:00

fix(tools): render complete lists and never print a bare OK #11

dsh closed this issue

2026-10-23 18:05:32 +00:00

dsh commented

2026-10-23 18:05:58 +00:00

Author

Owner

Fixed in 4d77e9f (fix(tools): render complete lists and never print a bare OK), merged to master (#11).

The formatter no longer slices to 20: it renders every row up to 100 and adds an explicit footer beyond that (… and N more — narrow the filter or page through.).
Live check (Forgejo 17, running plugin): gitea_issue_list on pvlb-infra/vps-setup (state=all, limit=50, page=1) returned all 28 rows; limit:5 still returns exactly 5 (covered by test/handlers-formatters.test.mjs).

Fixed in 4d77e9f (`fix(tools): render complete lists and never print a bare OK`), merged to `master` (#11). - The formatter no longer slices to 20: it renders every row up to 100 and adds an explicit footer beyond that (`… and N more — narrow the filter or page through.`). - Live check (Forgejo 17, running plugin): `gitea_issue_list` on `pvlb-infra/vps-setup` (`state=all`, `limit=50`, `page=1`) returned all **28** rows; `limit:5` still returns exactly 5 (covered by `test/handlers-formatters.test.mjs`).

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

2026-10-23 18:27:31 +00:00

feat(ci): publish tagged builds to the Forgejo npm registry; point the updater at it #12

dsh referenced this issue

2026-10-23 22:54:50 +00:00

feat(issues): gitea_issue_create cannot set labels, assignee or milestone #6

dsh referenced this issue

2026-10-24 01:25:16 +00:00

fix(timeline): gitea_issue_timeline omits label names, title changes and milestone/assignee payloads #34