fix(storage): evict construction cache at durable boundaries - #1081
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This comment has been minimized.
This comment has been minimized.
bda5d73 to
c34ae92
Compare
Durable construction can exhaust its memory envelope through file-backed cache. Shared filesystem readers and writers now bound active cache windows, synchronize writes before Linux cache advice, and carry measured synchronization evidence through construction and import receipts.
Closes #1110. Refs #951 and #952. #951 retains the full-lifecycle attribution and S20/conditional S22 host outcomes.
The integration fixes three verified defects: empty reads incorrectly marked unread input as exhausted; CAS payload copies discarded periodic synchronization counts; and Windows direct-file certification attempted to synchronize a read-only handle. Boundary tests preserve exact synchronization counts, bytes, hashes, reopened content, and cleanup. Existing Windows CI now exercises the direct-file regression. A reproduced ETXTBSY race in test shell fixtures is fixed by invoking the shell explicitly.
Validation on OVHC-AGENCY:
c34ae921. Squash-merged as581b44a2; fix(storage): reconcile bounded cache eviction synchronization #1110 is closed.No host-scale certification outcome is claimed by this implementation PR.