Batch security reviews into one process: 61 invocations paid 61 cold prefixes #174
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
external-review
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence-archived#174
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A 25-turn session never amortizes its cold start. Measured, 3.x era:
One process reviewing N diffs pays one cold prefix instead of N. 61 invocations paid 61 cold starts.
This is the second exit on #173 and the one reachable without an upstream change: batching also lands consecutive invocations inside the 5-minute window, so it fixes the TTL mismatch as a side effect rather than needing the TTL raised.
Open question: whether a batched review over N diffs finds what N single-diff reviews find. A per-commit review is scoped to one change on purpose, so this is a real trade rather than free.