Rust ORM Phase 1: Route observability collections through Rust data-daemon worker #263
Conversation
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
…njection - New workspace/list command: scans .git/continuum-worktrees/ on disk, merges WorkspaceStrategy in-memory state, returns git status per workspace. Supports --personaId filter. Generated via CommandGenerator. - ProjectContextSource RAG fix: falls back to main repo when no persona-specific workspace exists (solves chicken-and-egg — personas now see codebase context before first code/* tool use). Distinguishes "Shared Repository" vs "Your Workspace" with bootstrapping hint. - SentinelAutoConfig: auto-detects build/test/lint commands from code/shell/execute and injects sentinel classification rules. Wired into PersonaToolExecutor as fire-and-forget after shell execution starts. - Git cleanup: removed 39 stale undefined/* branches, 2 stale session worktrees, fast-forwarded 3 valid ai/ worktrees to HEAD.
…aemon worker Wire the existing Rust data-daemon worker (Unix socket IPC) into the DataDaemon's per-collection adapter routing. 10 write-heavy observability collections now go through Rust instead of TypeScript SQLite. Key changes: - DataDaemonServer: connectRustDataWorker() waits for socket, registers RustWorkerStorageAdapter for 10 collections, process.exit(1) if worker not available (no silent fallback) - DatabaseHandleRegistry: re-enable RustWorkerStorageAdapter import and 'rust' case in open() - DefaultStorageAdapterFactory: 'rust' case returns RustWorkerStorageAdapter - Rust data-daemon worker: PRAGMA table_info column filtering in data_create/data_update (and timed variants) to handle TypeScript entities with fields that don't map to SQL columns Verified: 1113 requests, 779 creates, 0 errors. Killing the Rust worker causes writes to fail (no fallback to TypeScript SQLite).
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.
Summary
cognition_state_snapshots,cognition_plan_records,cognition_plan_step_executions,cognition_self_state_updates,cognition_memory_operations,cognition_plan_replans,adapter_decision_logs,adapter_reasoning_logs,response_generation_logs,tool_execution_logsdata_create/data_updatenow filter columns viaPRAGMA table_infobefore INSERT/UPDATE (fixes 57 write errors from TypeScript entities with fields that don't map to SQL columns)process.exit(1)if Rust worker socket not available at startup; writes fail hard if worker dies mid-operation (proven by killing worker and observingECONNREFUSEDerrors)Verified
ECONNREFUSED(no silent fallback to TypeScript SQLite)users,chat_messages) continue through TypeScript SQLite unaffectedping,data/list,chat/sendall functionalRollback
Remove
await this.connectRustDataWorker();fromDataDaemonServer.initializeDeferred(). One line.Test plan