Skip to content

la pins: read a long listing in pages (from/next) - #82

Merged
wardviaene merged 1 commit into
mainfrom
la-pins-paged
Nov 20, 2026
Merged

wardviaene merged 1 commit into
mainfrom
la-pins-paged

Conversation

@wardviaene

Copy link
Copy Markdown
Member

Firmware with la_pins_paged (features rev 12, benchpod-firmware #206) pages a la_pins listing too large for one cloud reply: each reply carries the pins that fit and next; from continues there.

  • benchpod la pins reads the pod's status once; with la_pins_paged it follows next with from (and the same la), joins pins, takes levels and pull_dirs from the last reply (--json prints the joined reply without next). Capped at 16 replies, stops with a warning when next does not move forward.
  • Older firmware: the two-half fallback stays, and now also triggers on BP0054 (the cloud form of reply_too_large), not only BP0053.
  • Feature table synced to revision 12; README updated.
  • Tests with a fake pod that pages (full list, subset, single page, bad next, BP0054 halves).

🤖 Generated with Claude Code

On firmware with la_pins_paged (features rev 12) a reply that cannot carry every
pin says next; the CLI asks again with from (and the same la) and joins the pins,
levels and pull_dirs from the last reply. Capped at 16 replies; stops when next
does not move forward. Older firmware keeps the two-half fallback, now on BP0054
(cloud) as well as BP0053. Feature table synced to revision 12.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wardviaene
wardviaene merged commit f881857 into main Nov 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant