Skip to content

fix: raise the signed host_calls ceiling to 512 #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lr00rl merged 1 commit into from
Aug 11, 2026
Merged

fix: raise the signed host_calls ceiling to 512 #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion internal/plugin/invoke_budget.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,13 @@ const (
HostMaxInvokeTimeoutMS = 30_000
HostMaxInvokeStdoutBytes = 8 << 20
HostMaxInvokeStderrBytes = 1 << 20
HostMaxInvokeHostCalls = 64
// HostMaxInvokeHostCalls bounds what a signed manifest may declare per
// method. 64 was sized for CRUD shapes; the sub-store plugin's real shapes
// run past it — an export reattaches one program key per script file and
// the store caps at 256 records (2 + 256 = 258), and a migration is that
// plus three upstream fetches (263). 512 covers the store-bounded worst
// cases with headroom while still killing a runaway plugin.
HostMaxInvokeHostCalls = 512
)

// InvokeBudgetSpec is signed method-level runtime data. An absent budget stays
Expand Down