fix: bound Cursor blob-store memory - #845
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Maintainer triage status: this is valuable work. It bounds Cursor blobs while using scoped pins to protect active requests, has strong test coverage, and defines saturation behavior explicitly. It currently conflicts with |
Summary
setBlobArgsinstead of acknowledging a store that did not happenPart of #820. This is a focused request-lifetime lease implementation rather than #829 app-wide memory infrastructure.
Verification
bun test tests/cursor-*.test.ts(398 pass)bun run typecheckbun run privacy:scanCompatibility
Content-addressed IDs and get/set protobuf shapes remain unchanged. A single blob above 16 MiB or a request whose unique pinned blobs cannot fit 64 MiB now fails explicitly rather than evicting an in-flight reference or retaining unbounded data.