| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
|
Not sure whether this will be a problem, but this increases the binary size by 600KB. |
Sorry, something went wrong.
There was a problem hiding this comment.
Not saying whether or not we should land this, but https://github.com/nodejs/node/blob/main/deps/sqlite/unofficial.gni should be updated, and there should be at least one test for each new API to prevent regressions.
Sorry, something went wrong.
Good point. Also, I think it would be good to have some benchmarks on sqlite implementations. |
Sorry, something went wrong.
@cjihrig , what's the difference between .gyp and .gni file? |
Sorry, something went wrong.
They are for two different build systems. The .gyp file is used by the official build. The .gni file is used by the unofficial GN build. |
Sorry, something went wrong.
Thank you! |
Sorry, something went wrong.
Why not? And why not the Geopoly extension? |
Sorry, something went wrong.
For RBU, I didn't see it in better-sqlite3 or node-sqlite3. Geopoly seems like a good extension to have. |
Sorry, something went wrong.
On the other hand, the issue mentions the SQLite Amalgamation. I think we could have RBU enabled.
|
Sorry, something went wrong.
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files @@ Coverage Diff @@
## main #57621 +/- ##
==========================================
+ Coverage 90.22% 90.23% +0.01%
==========================================
Files 630 630
Lines 185054 185055 +1
Branches 36254 36219 -35
==========================================
+ Hits 166963 166985 +22
- Misses 11032 11037 +5
+ Partials 7059 7033 -26 see 45 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
There was a problem hiding this comment.
Small typo
Sorry, something went wrong.
There was a problem hiding this comment.
One comment, but changes LGTM.
Sorry, something went wrong.
Co-authored-by: Colin Ihrig <cjihrig@gmail.com>
| ); | ||
| }); | ||
|
|
||
| test('fts3 parenthesis', (t) => { |
There was a problem hiding this comment.
This is inconsistent with the rest, missing is enabled in its name.
Sorry, something went wrong.
There was a problem hiding this comment.
Still unsure whether or not we want all of these enabled, but giving this a LGTM so it's not stalled.
Sorry, something went wrong.
PR-URL: #57621 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
PR-URL: #57621 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
PR-URL: #57621 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
|
More common flags that are missing are SQLITE_ENABLE_UPDATE_DELETE_LIMIT and SQLITE_ENABLE_NULLS_LAST_IN_INDEX |
Sorry, something went wrong.
22.13 exposes node:sqlite but SQLite was built without FTS5 until 22.16 (nodejs/node#57621). Co-authored-by: Cursor <cursoragent@cursor.com>
…gelog - Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0 - Tests: storageGrowth nulls vs expect.anything(); EventLog CHECK relaxed - CHANGELOG [Unreleased]: cron exit validation (#1203) + Node bump - Biome-format cron exit validator / harness / install paths Co-authored-by: Cursor <cursoragent@cursor.com>
- Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0; sync verify/maintenance copy - Tests: storageGrowth null handling; EventLog CHECK relaxed - CHANGELOG [Unreleased]: maintenance LLM tier + Node bump - Biome-format touched config/CLI files Co-authored-by: Cursor <cursoragent@cursor.com>
- Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0; sync verify/maintenance copy - Tests: storageGrowth null handling; EventLog CHECK relaxed - CHANGELOG [Unreleased]: deprecated cron command handling + Node bump Co-authored-by: Cursor <cursoragent@cursor.com>
- Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0; sync verify/maintenance copy - Tests: storageGrowth null handling; EventLog CHECK relaxed - CHANGELOG [Unreleased]: Node requirement under Changed Co-authored-by: Cursor <cursoragent@cursor.com>
* Initial plan * Add JSON output to config command, features command, and consolidate-episodes deprecation notice Agent-Logs-Url: https://github.com/markus-lassfolk/openclaw-hybrid-memory/sessions/25f77f4e-1ea6-444b-b0b2-60f98bd13a4d Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * Update CHANGELOG with new CLI commands and fixes Agent-Logs-Url: https://github.com/markus-lassfolk/openclaw-hybrid-memory/sessions/25f77f4e-1ea6-444b-b0b2-60f98bd13a4d Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * fix(ci): Node 22.13 for node:sqlite; Biome-format hybrid-mem CLI - CI/security: pin Node 22 jobs to 22.13 (22.12 needs --experimental-sqlite) - engines, .nvmrc, docs: require >=22.13.0; sync verify/maintenance copy - Format cmd-config and register-corrections-and-pipeline with Biome Co-authored-by: Cursor <cursoragent@cursor.com> * fix(ci): require Node 22.16 for node:sqlite FTS5 support 22.13 exposes node:sqlite but SQLite was built without FTS5 until 22.16 (nodejs/node#57621). Co-authored-by: Cursor <cursoragent@cursor.com> * test: align audit-health and event-log expectations with Vitest and schema - expect.anything() does not match null (storageGrowth delta fields) - EventLog no longer applies CHECK on event_type after relaxation migration Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): config JSON contract, format validation, consolidate shim - Versioned config-view JSON summary + wal/ambient/futureDateProtection toggles. - features command emits features-only JSON; validate config --format. - consolidate-episodes exits 0 with deprecation warning; changelog aligned. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: anthropic-code-agent[bot] <242468646+Claude@users.noreply.github.com> Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> Co-authored-by: Ralph <ralph@openclaw.dev> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: OpenClaw Agent <agent@openclaw.dev>
…1214) * Initial plan * fix: add timeout protection and partial result handling to audit-health - Add `status` field ("ok"|"partial"|"failed") and `errors` array to AuditHealthReport schema - Keep backward-compatible `ok` field (deprecated) - Add 5000-row LIMIT to implicitFeedbackPrefixHistogram query to prevent scanning huge fact tables - Wrap prefix histogram in try-catch with error tracking - Add 5-second timeout for LanceDB size calculation (getStorageSizes) - Update strict mode to check both status and ok fields - Update markdown printer to show errors section - Update tests to validate new schema fields Fixes hang on long-lived stores by bounding expensive operations. Agent-Logs-Url: https://github.com/markus-lassfolk/openclaw-hybrid-memory/sessions/64bfcd5d-27d4-4a78-b223-6142f3a0b1ab Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * docs: add CHANGELOG entry for audit-health timeout fix Agent-Logs-Url: https://github.com/markus-lassfolk/openclaw-hybrid-memory/sessions/64bfcd5d-27d4-4a78-b223-6142f3a0b1ab Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * fix(ci): Node 22.16 + FTS5; Vitest audit-health/event-log; changelog - Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0; sync verify/maintenance copy - Tests: storageGrowth null handling; EventLog CHECK relaxed - CHANGELOG [Unreleased]: Node requirement under Changed Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): audit-health status, Lance size timeout, and changelog ref - Derive partial status when warnings or report errors exist; align legacy ok flag. - Record LanceDB du timeout in report.errors; kill du via execFile timeout. - Rename misleading EventLog test describe; changelog references #1214. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): detect implicit-feedback histogram truncation via LIMIT+1 Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: anthropic-code-agent[bot] <242468646+Claude@users.noreply.github.com> Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> Co-authored-by: Ralph <ralph@openclaw.dev> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: OpenClaw Agent <agent@openclaw.dev>
* Initial plan * Fix stale consolidate-episodes references in cron/verify * fix(ci): Node 22.16 + FTS5; Vitest audit-health/event-log; changelog - Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0; sync verify/maintenance copy - Tests: storageGrowth null handling; EventLog CHECK relaxed - CHANGELOG [Unreleased]: deprecated cron command handling + Node bump Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): robust HM_EXIT scan for deprecated cron steps - Recursively collect recent .exit.txt under cron-hybrid-mem (flat + subdirs). - Per-file read isolation; escape regex metacharacters in deprecated tokens. - Tests: mkdtemp + cleanup; cover exit ledger path collection. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): skip deprecated-cron warnings for feature-gated jobs Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: openai-code-agent[bot] <242516109+Codex@users.noreply.github.com> Co-authored-by: Ralph <ralph@openclaw.dev> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: OpenClaw Agent <agent@openclaw.dev>
* Initial plan * feat(memory-hybrid): add maintenance LLM tier and routing warnings Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * fix(ci): Node 22.16 + FTS5; Vitest audit-health/event-log; changelog - Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0; sync verify/maintenance copy - Tests: storageGrowth null handling; EventLog CHECK relaxed - CHANGELOG [Unreleased]: maintenance LLM tier + Node bump - Biome-format touched config/CLI files Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): align reflection routing with maintenance tier and docs - Route reflect/reflect-rules/reflect-meta through maintenance tier and default reflectionConfig.model from that tier. - Derive extraction heavy-model warnings from filtered tier preferences. - Correct distill.extractionModelTier schema/docs: unset defaults to nano. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): derive dream-cycle heavy warning from filtered maintenance tier Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: openai-code-agent[bot] <242516109+Codex@users.noreply.github.com> Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> Co-authored-by: Ralph <ralph@openclaw.dev> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: OpenClaw Agent <agent@openclaw.dev>
…on (#1204) * Initial plan * Add exit ledger validation for cron jobs - Create cron-exit-validator.ts with structured validation - Add validate-cron-exit CLI command for internal use - Update cron job bash harness with validation instructions - Add comprehensive tests for exit ledger parsing and validation - Register new validation command in CLI Agent-Logs-Url: https://github.com/markus-lassfolk/openclaw-hybrid-memory/sessions/cd60b52e-d486-4166-b77f-63a3040389a2 Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * Add message normalization to fix obsolete cron commands - Update existing cron job messages when normalizeExisting=true - Remove obsolete command references (e.g., consolidate-episodes) - Convert tests to vitest format - All 14 tests passing Agent-Logs-Url: https://github.com/markus-lassfolk/openclaw-hybrid-memory/sessions/cd60b52e-d486-4166-b77f-63a3040389a2 Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * Add comprehensive documentation for cron exit validation - Document validation behavior and expected outcomes - Explain migration path for existing installations - Detail config-based skipping mechanism - List acceptance criteria and testing coverage Agent-Logs-Url: https://github.com/markus-lassfolk/openclaw-hybrid-memory/sessions/cd60b52e-d486-4166-b77f-63a3040389a2 Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> * fix(ci): Node 22.16 + FTS5; Vitest audit-health/event-log tests; changelog - Pin CI/security to Node 22.16 (node:sqlite + FTS5, nodejs/node#57621) - engines, .nvmrc, docs: require >=22.16.0 - Tests: storageGrowth nulls vs expect.anything(); EventLog CHECK relaxed - CHANGELOG [Unreleased]: cron exit validation (#1203) + Node bump - Biome-format cron exit validator / harness / install paths Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): use Number.parseInt in cron-exit-validator (Biome error) Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): treat all-missing exit ledger as failed, not skipped Empty or step-less HM_EXIT cannot distinguish guard skip from abort before hm_step; report failure so validate-cron-exit surfaces the error. Co-authored-by: chatgpt-codex-connector <noreply@openai.com> Co-authored-by: Cursor <cursoragent@cursor.com> * fix(memory-hybrid): respect messageOverrides during cron normalizeExisting Apply overrides to payload.message for agentTurn jobs and skip canonical message replacement when a per-job override is provided. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(cron): treat empty exit ledger as skipped when log shows feature-gated skip Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: anthropic-code-agent[bot] <242468646+Claude@users.noreply.github.com> Co-authored-by: markus-lassfolk <3661143+markus-lassfolk@users.noreply.github.com> Co-authored-by: Ralph <ralph@openclaw.dev> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: chatgpt-codex-connector <noreply@openai.com> Co-authored-by: OpenClaw Agent <agent@openclaw.dev>
node:sqlite only ships FTS5 compiled in by default starting at Node 22.16.0 (nodejs/node#57621), not 22.13 as previously declared. Below that patch, the first `bound index` call throws `no such module: fts5` from saveFunctionGraph. This had been silently broken since 0.1.0 shipped -- CI itself was pinned to 22.13.x and had been red since the first public push. Found while validating the new release workflow against a real GitHub Actions runner. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* coverage.yml: stop pinning to .nvmrc's exact floor version Discovered why the workflow failed after merging: node:sqlite only gained FTS5 support in Node 22.16.0 (nodejs/node#57621, verified). This repo's stated floor (.nvmrc/engines.node: >=22.13.0) predates that, so pinning to it exactly makes test/organize.test.js's index-db-backed tests throw 'no such module: fts5' — a real, pre-existing gap ci.yml never caught because it floats to whatever '22.x' currently resolves to (22.23.2), not the literal floor. This commit only fixes the coverage workflow (match ci.yml's floating 22.x). Whether to bump the actual floor to >=22.16.0 is a separate, bigger decision — left to the maintainer. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * Bump the Node floor to >=22.16.0, where node:sqlite FTS5 actually works .nvmrc, package.json/package-lock.json's engines.node, README's badge + Requirements line, and CONTRIBUTING.md's Requirements all bumped 22.13 -> 22.16. Now that the floor genuinely has FTS5, coverage.yml's workaround from the previous commit (floating '22.x' instead of node-version-file: .nvmrc) is unnecessary — reverted back to .nvmrc, which is now correct again and will keep tracking whatever this repo's floor actually is. npm install also picked up a pre-existing, unrelated drift in package-lock.json's own version field (0.1.0 -> 0.1.5, matching package.json — lockfile just hadn't been regenerated in a while). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
This PR enables flags that are common to other sqlite players in Node.js ecosystem:
This is related to #56476, even though it does not enable the RBU extension.
I see this as a good step toward the stabilization since it will make it easier for people from other dependencies.