fix: implement type-aware storage prefixes for commits and trees
Fixed critical bug where BlobStorage hardcoded 'blob:' prefix in 10 locations,
ignoring the 'type' parameter passed to write operations. This caused:
- Commits stored as blob:${hash} instead of commit:${hash}
- Trees stored as blob:${hash} instead of tree:${hash}
- brain.getHistory() returning empty arrays
Changes:
- src/storage/cow/BlobStorage.ts: Implement type-aware prefixes in 10 methods
- write(), read(), has(), delete(), getMetadata(), listBlobs()
- writeMultipart(), incrementRefCount(), decrementRefCount()
- tests/integration/cow-commit-storage.test.ts: Add regression tests (6 tests)
Backward compatibility: read() auto-detects type by trying commit:, tree:, blob:
prefixes, allowing old blob:* files to be read.
Works for ALL storage adapters (filesystem, S3, Azure, GCS, R2, memory, OPFS).
Fixes: Workshop team bug report (getHistory returns empty despite commits)
Tests: 6/6 new tests pass, 6/6 existing COW tests pass (no regressions)
2025-11-04 15:03:05 -08:00
/ * *
* Regression test for v5 . 3.3 bug fix :
* Commits were being stored as blob :$ { hash } instead of commit :$ { hash }
*
* This caused getHistory ( ) to return empty arrays because it couldn ' t find
* commit objects on disk .
*
* Related bugs :
fix: recalibrate find({ limit }) cap + two-tier enforcement + caller location
Brainy 7.30.0 introduced a memory-derived synchronous cap on `find({ limit })`
to prevent OOM. The cap was sound in intent but ~4x too conservative in
calibration: assumed 100 KB per result while typical entity footprint is 7-10 KB
(384-dim float32 vector ≈ 1.5 KB + standard fields + metadata). On a 900 MB
free-memory box the cap derived to 9000 — breaking common safety-cap patterns
like `find({ type, where, limit: 10_000 })` that typically return 10-500
entities. Surfaced as a runtime regression with cascading 500s degrading
production dashboards.
Three concurrent fixes:
A. RECALIBRATE THE FORMULA
- src/utils/paramValidation.ts:175,196,212 — the three memory-derived priorities
(reservedQueryMemory / containerMemory / freeMemory) all divided by
100 * 1024 * 1024 (100 KB per result, ~10-15x over conservative). Replaced
with a new MAX_LIMIT_KB_PER_RESULT = 25 constant that matches observed
entity size.
- Result: 4 GB container cap goes 10_000 → 40_000; 2 GB cap goes 5_000 →
20_000; 900 MB free-memory cap goes 9_000 → ~36_000. 100k hard ceiling
unchanged. `maxQueryLimit` / `reservedQueryMemory` constructor overrides
unchanged in behavior.
B. TWO-TIER ENFORCEMENT (warn-then-throw)
- Below cap (limit <= maxLimit): silent pass, unchanged.
- Soft tier (maxLimit < limit <= 2 * maxLimit): NEW — one-time warning per
call site (dedup keyed on caller stack frame + limit value), query
proceeds. Pre-7.30.2 code that relied on the cap silently allowing typical
safety-cap limits keeps working; the warning teaches the recipe so consumers
can fix it intentionally.
- Hard tier (limit > 2 * maxLimit): throw with the same teaching message
format. Real OOM territory; the cap stops being a recommendation and becomes
a guardrail.
- The 2x soft margin absorbs typical safety-cap patterns (limit: 10_000
against a 9 K-cap box) without disabling OOM protection. Real OOM territory
on a JS in-memory brain is hundreds of thousands of results, not 10x the
safety cap.
C. IMPROVED ERROR / WARNING MESSAGE
- Same shape as the 7.30.1 enforcement-error messages: state the problem,
name the three escape valves (maxQueryLimit / reservedQueryMemory /
pagination), include caller location, link to docs.
- Extracted findCallerLocation() helper from brainy.ts to a new
src/utils/callerLocation.ts so both the subtype enforcement (7.30.1) and
the limit enforcement (7.30.2) share one implementation without circular
imports.
DOCS
- New docs/guides/find-limits.md (public: true) — full reference: why the cap
exists, the four memory sources the auto-config considers, the three escape
valves with when-to-use-which guidance, and an explicit "pagination is the
future-proof pattern" callout (8.0 may tighten the cap further; pagination
keeps working unchanged).
- docs/api/README.md find() entry gets a one-paragraph `limit` tip + pointer
to the new guide.
- RELEASES.md v7.30.2 entry.
TESTS
- New tests/integration/find-limits.test.ts (9 tests): below-cap silent pass;
soft-tier warns once per call site (dedup verified by exercising same vs.
different source lines via wrapper closures); soft-tier message format
(names all three escape valves + docs link); soft-tier message includes
caller location; hard-tier throws; hard-tier message format same as
soft-tier; consumer maxQueryLimit override raises the cap and shifts both
tiers accordingly; pre-7.30.2 regression scenario explicitly covered.
- tests/unit/utils/memoryLimits.test.ts — 4 tests updated for the recalibrated
cap values (hardcoded expected numbers bumped 4x to match new 25 KB/result
assumption).
- tests/unit/utils/paramValidation.test.ts — auto-limit test extended to cover
the three-tier semantics (below-cap pass / soft-tier silent / hard-tier
throw).
- Existing suites unchanged: subtype-and-facets 26/26, verb-subtype-and-
enforcement 30/30, strict-mode-self-test 13/13. Unit 1468/1468.
CORTEX COMPATIBILITY
- Zero Cortex changes required. Every change is JS-side: formula recalibration
runs in ValidationConfig.constructor(), two-tier enforcement runs in
validateFindParams(), both fire before any storage / index / Cortex call.
- The new guide notes that Brainy 8.0's Datomic-style Db.find() may tighten
per-call limits to keep snapshot semantics cheap; pagination remains the
pattern that's guaranteed to keep working.
REPO-WIDE CLEANUP
Brainy is the only Soulcraft project that is open source. This commit also
scrubs closed-source product names and product-specific class/field references
from every tracked file in the repo (src/, docs/, tests/, RELEASES.md,
CHANGELOG.md). Consumer-reported bugs, regression scenarios, and release
notes now refer to "a consumer", "a downstream application", "a production
deployment", or "an internal report" — never to the named product. Two
product-named test files renamed to neutral diagnostic names. CLAUDE.md gains
a project-level guard rule documenting the policy and an example list of the
identifiers that may not appear in tracked code.
Verification
- npx tsc --noEmit: clean
- npm test: 1468 / 1468 unit
- All four integration subtype + verb + strict + find-limits suites: 78/78
- npm run build: clean
- Closed-source product reference audit: clean
2026-06-08 12:34:05 -07:00
* - v5 . 3.0 snapshot regression filed via consumer bug report ( BRAINY_V5 . 3.0 _SNAPSHOT_BUG_REPORT . md , internal )
fix: implement type-aware storage prefixes for commits and trees
Fixed critical bug where BlobStorage hardcoded 'blob:' prefix in 10 locations,
ignoring the 'type' parameter passed to write operations. This caused:
- Commits stored as blob:${hash} instead of commit:${hash}
- Trees stored as blob:${hash} instead of tree:${hash}
- brain.getHistory() returning empty arrays
Changes:
- src/storage/cow/BlobStorage.ts: Implement type-aware prefixes in 10 methods
- write(), read(), has(), delete(), getMetadata(), listBlobs()
- writeMultipart(), incrementRefCount(), decrementRefCount()
- tests/integration/cow-commit-storage.test.ts: Add regression tests (6 tests)
Backward compatibility: read() auto-detects type by trying commit:, tree:, blob:
prefixes, allowing old blob:* files to be read.
Works for ALL storage adapters (filesystem, S3, Azure, GCS, R2, memory, OPFS).
Fixes: Workshop team bug report (getHistory returns empty despite commits)
Tests: 6/6 new tests pass, 6/6 existing COW tests pass (no regressions)
2025-11-04 15:03:05 -08:00
* - Root cause : BlobStorage.ts hardcoded 'blob:' prefix in 9 locations
* /
import { describe , it , expect , beforeEach , afterEach } from 'vitest'
import { Brainy } from '../../src/brainy.js'
import * as fs from 'fs/promises'
import * as path from 'path'
describe ( 'COW Commit Storage Type-Aware Prefixes' , ( ) = > {
let brain : Brainy
let testDir : string
beforeEach ( async ( ) = > {
testDir = path . join ( '/tmp' , ` brainy-cow-test- ${ Date . now ( ) } ` )
brain = new Brainy ( {
storage : {
type : 'filesystem' ,
path : testDir ,
branch : 'main' ,
enableCompression : true
} ,
disableAutoRebuild : true ,
silent : true
} )
await brain . init ( )
} )
afterEach ( async ( ) = > {
// Clean up test directory
try {
await fs . rm ( testDir , { recursive : true , force : true } )
} catch ( err ) {
// Ignore cleanup errors
}
} )
it ( 'should store commits with commit: prefix (not blob: prefix)' , async ( ) = > {
// Create a commit
await brain . commit ( 'Test commit for type-aware storage' )
// Check filesystem directly
const cowDir = path . join ( testDir , '_cow' )
const files = await fs . readdir ( cowDir )
// Should have commit: files
const commitFiles = files . filter ( f = > f . startsWith ( 'commit:' ) )
expect ( commitFiles . length ) . toBeGreaterThan ( 0 )
// Should NOT have blob: files that are actually commits
// (blob: files should only be for actual blob data)
const blobFiles = files . filter ( f = > f . startsWith ( 'blob:' ) && ! f . includes ( '-meta' ) )
// Read metadata of blob files to ensure none are commits
for ( const blobFile of blobFiles ) {
const metaFile = blobFile . replace ( 'blob:' , 'blob:-meta:' )
if ( files . includes ( metaFile ) ) {
const metaPath = path . join ( cowDir , metaFile )
const metaContent = await fs . readFile ( metaPath , 'utf8' )
const metadata = JSON . parse ( metaContent )
expect ( metadata . type ) . not . toBe ( 'commit' )
}
}
} )
it ( 'should allow getHistory() to retrieve commits' , async ( ) = > {
// Create multiple commits
await brain . commit ( 'First commit' )
await brain . add ( {
data : 'Testing commit storage' ,
type : 'concept'
} )
await brain . commit ( 'Second commit with entity' )
// Get history - should NOT be empty
const history = await brain . getHistory ( { limit : 10 } )
expect ( history ) . toBeDefined ( )
expect ( Array . isArray ( history ) ) . toBe ( true )
expect ( history . length ) . toBeGreaterThanOrEqual ( 2 )
// Verify commit structure
expect ( history [ 0 ] ) . toHaveProperty ( 'hash' )
expect ( history [ 0 ] ) . toHaveProperty ( 'message' )
expect ( history [ 0 ] ) . toHaveProperty ( 'timestamp' )
expect ( history [ 0 ] ) . toHaveProperty ( 'author' )
} )
it ( 'should store trees with tree: prefix (if trees are created)' , async ( ) = > {
// Add an entity and commit
await brain . add ( {
data : 'Testing tree storage' ,
type : 'concept'
} )
await brain . commit ( 'Commit with tree' )
// Check filesystem - trees might or might not be created depending on implementation
// The important thing is that IF trees are created, they use tree: prefix
const cowDir = path . join ( testDir , '_cow' )
const files = await fs . readdir ( cowDir )
// Verify commit files exist (this is the critical part)
const commitFiles = files . filter ( f = > f . startsWith ( 'commit:' ) )
expect ( commitFiles . length ) . toBeGreaterThan ( 0 )
// If tree files exist, they should use tree: prefix (not blob:)
const treeFiles = files . filter ( f = > f . startsWith ( 'tree:' ) )
const blobTrees = files . filter ( f = > f . startsWith ( 'blob:' ) && ! f . includes ( '-meta' ) )
// Trees should be in tree: files, not blob: files
// (Or no tree files at all if implementation doesn't create them)
expect ( blobTrees . filter ( f = > f . includes ( 'tree' ) ) . length ) . toBe ( 0 )
} )
it ( 'should maintain backward compatibility with old blob: prefix' , async ( ) = > {
// This test verifies that read() auto-detects type by trying multiple prefixes
// We'll verify this by checking that the auto-detection code works
// Create a commit normally (will use commit: prefix)
await brain . commit ( 'Test commit for backward compat check' )
// The commit should be readable even though read() tries multiple prefixes
const history = await brain . getHistory ( { limit : 1 } )
expect ( history . length ) . toBe ( 1 )
// Verify the commit hash is readable via BlobStorage
const blobStorage = ( brain as any ) . storage . blobStorage
const commitHash = history [ 0 ] . hash
// This should work via auto-detection
const readData = await blobStorage . read ( commitHash )
expect ( readData ) . toBeDefined ( )
expect ( readData . length ) . toBeGreaterThan ( 0 )
} )
it ( 'should handle fork() and snapshot creation with proper commit storage' , async ( ) = > {
// Add some data
await brain . add ( {
data : 'Testing snapshots' ,
type : 'concept'
} )
await brain . commit ( 'Commit before fork' )
// Create a fork (snapshot branch)
const snapshotBranch = ` snapshot- ${ Date . now ( ) } `
await brain . fork ( snapshotBranch )
// Get history - should work (this is the critical test)
const history = await brain . getHistory ( { limit : 10 } )
expect ( history . length ) . toBeGreaterThanOrEqual ( 1 )
// History working proves commits are stored correctly
} )
it ( 'should properly delete commits with type-aware prefix' , async ( ) = > {
// Create a commit
await brain . commit ( 'Commit to delete' )
const history = await brain . getHistory ( { limit : 1 } )
const commitHash = history [ 0 ] . hash
// Delete via BlobStorage
const blobStorage = ( brain as any ) . storage . blobStorage
await blobStorage . delete ( commitHash )
// Verify deleted
const exists = await blobStorage . has ( commitHash )
expect ( exists ) . toBe ( false )
// Verify files removed from disk
const cowDir = path . join ( testDir , '_cow' )
const files = await fs . readdir ( cowDir )
const commitFile = files . find ( f = > f . includes ( commitHash ) && f . startsWith ( 'commit:' ) )
expect ( commitFile ) . toBeUndefined ( )
} )
} )