chore: back-merge main → dev (v0.7.6 version bumps) - #136
Merged
Conversation
…131) Bulk ingest of a large note/file produces one MemoryEntry whose serialized size alone exceeds the STM memory budget (1MB in the standard profile). store() tried to prune space for it, but an entry that alone overflows the budget can never be made to fit, so once the STM emptied it returned a hard "STM memory capacity exceeded" error and aborted the whole ingest ("Motor no disponible"). The byte budget is a pruning target, not an admission gate: STM is a transient buffer that consolidates into LTM (which is bounded by count, not bytes). store() now prunes only while pruning makes progress and admits the entry over budget once it cannot free more. This also fixes a latent infinite loop: when every resident entry was already consolidated (prune_one leaves those in place) the prune loop spun forever. prune_one now returns whether it evicted anything so store() can stop. Covered by test_oversized_entry_is_accepted_not_rejected and test_store_terminates_when_only_consolidated_entries_remain.
Merge dev → main: cortex aingle_path, STM oversized-entry fix, byte-bounded ingest chunking
Per-crate version bumps for the changes landed since v0.7.5: - ineru 0.7.4 -> 0.7.5: short-term memory admits an entry larger than its byte budget instead of erroring, so bulk ingest never stalls. - aingle_ingest 0.7.1 -> 0.7.2: byte-bounded chunking; large/minified files no longer produce a single oversized chunk. - aingle_cortex 0.7.5 -> 0.7.6: aingle_path (shortest verified connection between two notes) and the ingest improvements above. Dependents pin these with caret "0.7", so the patch/minor bumps resolve without changes. Cargo.lock refreshed.
release: aingle 0.7.6 (ineru 0.7.5, aingle_ingest 0.7.2, cortex 0.7.6)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Syncs
devwith the 0.7.6 release commits onmain(per-crate version bumps + Cargo.lock) so the next dev→main integration doesn't conflict on version lines. No code changes beyond what already exists on both branches.