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
267 lines
8 KiB
TypeScript
267 lines
8 KiB
TypeScript
/**
|
|
* Fork Persistence Integration Test
|
|
*
|
|
* Tests the complete fork() → listBranches() → checkout() workflow
|
|
* to prevent regression of the v5.3.6 bug where fork() silently failed
|
|
* to persist branches to storage (internal bug report).
|
|
*
|
|
* @see https://github.com/soulcraftlabs/brainy/issues/XXX
|
|
*/
|
|
|
|
import { describe, it, expect, beforeEach, afterEach } from 'vitest'
|
|
import { Brainy } from '../../src/brainy'
|
|
import * as fs from 'fs'
|
|
import * as path from 'path'
|
|
|
|
describe('Fork Persistence (v5.3.6 Bug Fix)', () => {
|
|
let brain: Brainy
|
|
let testDir: string
|
|
|
|
beforeEach(async () => {
|
|
// Use filesystem storage to mirror cloud storage behavior
|
|
testDir = `/tmp/brainy-fork-test-${Date.now()}`
|
|
brain = new Brainy({
|
|
storage: {
|
|
adapter: 'filesystem',
|
|
path: testDir
|
|
},
|
|
silent: true
|
|
})
|
|
await brain.init()
|
|
})
|
|
|
|
afterEach(async () => {
|
|
// Cleanup test directory
|
|
if (fs.existsSync(testDir)) {
|
|
fs.rmSync(testDir, { recursive: true, force: true })
|
|
}
|
|
})
|
|
|
|
it('should persist forked branches to storage', async () => {
|
|
// Add data and commit
|
|
await brain.add({ data: { value: 1 }, type: 'concept' })
|
|
const commitId = await brain.commit({
|
|
message: 'Initial commit',
|
|
author: 'test@example.com'
|
|
})
|
|
expect(commitId).toBeTruthy()
|
|
|
|
// Fork a new branch
|
|
const branchName = `test-branch-${Date.now()}`
|
|
await brain.fork(branchName, {
|
|
author: 'test@example.com',
|
|
message: 'Test fork for persistence'
|
|
})
|
|
|
|
// CRITICAL: Verify branch exists in storage (this would fail in v5.3.5)
|
|
const branches = await brain.listBranches()
|
|
expect(branches).toContain(branchName)
|
|
expect(branches).toContain('main')
|
|
})
|
|
|
|
it('should allow checkout of forked branch', async () => {
|
|
// Setup: Add data, commit, fork
|
|
await brain.add({ data: { value: 1 }, type: 'concept' })
|
|
await brain.commit({
|
|
message: 'Initial commit',
|
|
author: 'test@example.com'
|
|
})
|
|
|
|
const branchName = `checkout-test-${Date.now()}`
|
|
await brain.fork(branchName, {
|
|
author: 'test@example.com',
|
|
message: 'Test fork for checkout'
|
|
})
|
|
|
|
// CRITICAL: Checkout should succeed (this would fail in v5.3.5)
|
|
await expect(brain.checkout(branchName)).resolves.not.toThrow()
|
|
|
|
// Verify we're on the new branch
|
|
const currentBranch = await brain.getCurrentBranch()
|
|
expect(currentBranch).toBe(branchName)
|
|
})
|
|
|
|
it('should persist fork across multiple storage operations', async () => {
|
|
// Create initial state
|
|
await brain.add({ data: { step: 1 }, type: 'concept' })
|
|
await brain.commit({
|
|
message: 'Step 1',
|
|
author: 'test@example.com'
|
|
})
|
|
|
|
// Fork branch 1
|
|
const branch1 = `branch-1-${Date.now()}`
|
|
await brain.fork(branch1, {
|
|
author: 'test@example.com',
|
|
message: 'Fork 1'
|
|
})
|
|
|
|
// Add more data on main
|
|
await brain.add({ data: { step: 2 }, type: 'concept' })
|
|
await brain.commit({
|
|
message: 'Step 2 on main',
|
|
author: 'test@example.com'
|
|
})
|
|
|
|
// Fork branch 2
|
|
const branch2 = `branch-2-${Date.now()}`
|
|
await brain.fork(branch2, {
|
|
author: 'test@example.com',
|
|
message: 'Fork 2'
|
|
})
|
|
|
|
// Verify both branches exist
|
|
const branches = await brain.listBranches()
|
|
expect(branches).toContain('main')
|
|
expect(branches).toContain(branch1)
|
|
expect(branches).toContain(branch2)
|
|
|
|
// Verify all branches are accessible
|
|
await expect(brain.checkout(branch1)).resolves.not.toThrow()
|
|
await expect(brain.checkout(branch2)).resolves.not.toThrow()
|
|
await expect(brain.checkout('main')).resolves.not.toThrow()
|
|
})
|
|
|
|
it('should return new Brainy instance pointing to fork', async () => {
|
|
// Verify fork() returns a working Brainy instance on the new branch
|
|
|
|
await brain.add({ data: { value: 1 }, type: 'concept' })
|
|
await brain.commit({
|
|
message: 'Initial commit',
|
|
author: 'test@example.com'
|
|
})
|
|
|
|
// Fork and get new instance
|
|
const validBranch = `return-test-${Date.now()}`
|
|
const forkedBrain = await brain.fork(validBranch, {
|
|
author: 'test@example.com',
|
|
message: 'Test fork return value'
|
|
})
|
|
|
|
// Verify the returned instance is on the new branch
|
|
const forkCurrentBranch = await forkedBrain.getCurrentBranch()
|
|
expect(forkCurrentBranch).toBe(validBranch)
|
|
|
|
// Verify original instance is still on main
|
|
const mainCurrentBranch = await brain.getCurrentBranch()
|
|
expect(mainCurrentBranch).toBe('main')
|
|
|
|
// Verify both instances can see the branch
|
|
const mainBranches = await brain.listBranches()
|
|
const forkBranches = await forkedBrain.listBranches()
|
|
expect(mainBranches).toContain(validBranch)
|
|
expect(forkBranches).toContain(validBranch)
|
|
})
|
|
|
|
it('should handle snapshot naming convention (consumer use case)', async () => {
|
|
// Reproduce exact Consumer snapshot workflow
|
|
await brain.add({ data: { test: true }, type: 'concept' })
|
|
|
|
const commitId = await brain.commit({
|
|
message: 'Consumer snapshot test',
|
|
author: 'workshop@example.com'
|
|
})
|
|
|
|
// Use the consumer's exact naming convention
|
|
const timestamp = Date.now()
|
|
const snapshotBranch = `snapshot-${timestamp}`
|
|
|
|
// Create snapshot branch (this is what failed in the consumer report)
|
|
await brain.fork(snapshotBranch, {
|
|
author: 'workshop@example.com',
|
|
message: `Snapshot: Consumer test`,
|
|
metadata: {
|
|
timestamp,
|
|
userId: 'test-user',
|
|
isSnapshot: true,
|
|
snapshotCommit: commitId
|
|
}
|
|
})
|
|
|
|
// Verify snapshot can be listed
|
|
const branches = await brain.listBranches()
|
|
expect(branches).toContain(snapshotBranch)
|
|
|
|
// Verify snapshot can be restored (checked out)
|
|
await expect(brain.checkout(snapshotBranch)).resolves.not.toThrow()
|
|
|
|
// Verify we're on the snapshot branch
|
|
const currentBranch = await brain.getCurrentBranch()
|
|
expect(currentBranch).toBe(snapshotBranch)
|
|
})
|
|
|
|
it('should verify _cow paths are not branch-scoped', async () => {
|
|
// This test verifies the resolveBranchPath fix works correctly
|
|
// by checking that COW metadata is accessible globally
|
|
|
|
await brain.add({ data: { value: 1 }, type: 'concept' })
|
|
await brain.commit({
|
|
message: 'Test commit',
|
|
author: 'test@example.com'
|
|
})
|
|
|
|
const branch1 = `branch-a-${Date.now()}`
|
|
const branch2 = `branch-b-${Date.now()}`
|
|
|
|
// Create two branches
|
|
await brain.fork(branch1, {
|
|
author: 'test@example.com',
|
|
message: 'Branch A'
|
|
})
|
|
|
|
await brain.fork(branch2, {
|
|
author: 'test@example.com',
|
|
message: 'Branch B'
|
|
})
|
|
|
|
// From any branch, we should be able to list ALL branches
|
|
// This proves COW metadata is global, not branch-scoped
|
|
await brain.checkout(branch1)
|
|
let branches = await brain.listBranches()
|
|
expect(branches).toContain('main')
|
|
expect(branches).toContain(branch1)
|
|
expect(branches).toContain(branch2)
|
|
|
|
await brain.checkout(branch2)
|
|
branches = await brain.listBranches()
|
|
expect(branches).toContain('main')
|
|
expect(branches).toContain(branch1)
|
|
expect(branches).toContain(branch2)
|
|
|
|
await brain.checkout('main')
|
|
branches = await brain.listBranches()
|
|
expect(branches).toContain('main')
|
|
expect(branches).toContain(branch1)
|
|
expect(branches).toContain(branch2)
|
|
})
|
|
|
|
it('should persist fork with metadata', async () => {
|
|
// Test that metadata is preserved in fork
|
|
await brain.add({ data: { value: 1 }, type: 'concept' })
|
|
await brain.commit({
|
|
message: 'Test commit',
|
|
author: 'test@example.com'
|
|
})
|
|
|
|
const branchName = `metadata-test-${Date.now()}`
|
|
const metadata = {
|
|
timestamp: Date.now(),
|
|
userId: 'test-user-123',
|
|
customField: 'test-value',
|
|
nested: { data: true }
|
|
}
|
|
|
|
await brain.fork(branchName, {
|
|
author: 'test@example.com',
|
|
message: 'Fork with metadata',
|
|
metadata
|
|
})
|
|
|
|
// Verify branch exists
|
|
const branches = await brain.listBranches()
|
|
expect(branches).toContain(branchName)
|
|
|
|
// Verify branch is accessible
|
|
await expect(brain.checkout(branchName)).resolves.not.toThrow()
|
|
})
|
|
})
|