Skip to content

la_pins: read a long listing in pages (from/next) - #135

Merged
wardviaene merged 2 commits into
mainfrom
la-pins-paged
Nov 20, 2026
Merged

wardviaene merged 2 commits 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.

  • SDK la_pins: when the pod lists la_pins_paged, follows next with "from": next (and the same la), joins pins, takes pull_dirs from the last reply. Capped at 16 replies, stops when next does not move forward.
  • Older firmware: the two-half la fallback on BP0053/BP0054 stays.
  • MCP la_pins calls the SDK, so it pages too.
  • Feature table synced to revision 12; changelog entry under 4.0.1 (not released).
  • Unit tests with a fake pod that pages (full list, subset with la, single page, bad next, no feature).

🤖 Generated with Claude Code

wardviaene and others added 2 commits November 20, 2026 15:15
On firmware with la_pins_paged (features rev 12) a reply that cannot carry every
pin says next; the SDK asks again with from (and the same la) and joins the pins,
pull_dirs from the last reply. Capped at 16 replies; stops when next does not
move forward. Older firmware keeps the two-half fallback on BP0053/BP0054.
Feature table synced to revision 12. The MCP la_pins tool goes through the SDK.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wardviaene
wardviaene merged commit ebccf46 into main Nov 20, 2026
12 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