Skip to content

fix(vector): load extension before indexed embedding deletes#82

Open
100yenadmin wants to merge 4 commits into
reconcile/r18-vector-diagnosticsfrom
reconcile/r19a-vector-delete-reopen
Open

fix(vector): load extension before indexed embedding deletes#82
100yenadmin wants to merge 4 commits into
reconcile/r18-vector-diagnosticsfrom
reconcile/r19a-vector-delete-reopen

Conversation

@100yenadmin

Copy link
Copy Markdown
Member

Fixes #81.

Closes the P0 incremental HNSW deletion blocker discovered by the first OpenClaw-scale canary.

Change

  • Load LadybugDB VECTOR with load-only before deleteNodesForFiles() mutates CodeEmbedding.
  • Add a real persisted-HNSW close/reopen regression test.

No download or install is permitted on the delete path. Unindexed embedding tables keep their existing behavior; a persisted HNSW index without a loadable extension still fails loudly.

Proof

  • Red: close/reopen regression failed with the exact LadybugDB binder error.
  • Green: lbug-vector-extension.test.ts 9/9 passed.
  • Delete matrix: 13/13 passed across vector and batched-delete integration files.
  • Large subprocess interruption/recovery: 1/1 passed in 245.64 seconds.
  • npm run build: passed.
  • The disposable OpenClaw canary failure was nonzero and preserved a dirty marker; no live index was used.

Boundary

No package publication, release, deployment, runtime rollout, default-branch merge, live-index mutation, or global extension install is included.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8708c894-434e-4477-97d5-36c1c22aaa9d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch reconcile/r19a-vector-delete-reopen

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Jul 13, 2026

Copy link
Copy Markdown

✨ PR Autofix

Found fixable formatting / unused-import issues across 229 changed lines. Comment /autofix on this PR to apply them, or run npm run lint:fix && npm run format locally.

{"schema":"gitnexus.pr-autofix/v2","state":"fixes-available","pr_number":82,"changed_lines":229,"head_sha":"e41431d92afe6afb48affa486995097907724395","run_id":"29278279462","apply_command":"/autofix"}

@evaos-code-review-bot

evaos-code-review-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown

evaOS review status: failed

PR: #82 - fix(vector): load extension before indexed embedding deletes
Head: ea1f59a233a712ceaa995453537bc5b62ce98415
Updated: 2026-07-13T15:05:37.159Z

evaOS review failed for this head and needs retry or operator attention.

Automation note: agents should wait for this comment to reach completed, stale_head, closed_or_merged_before_review, skipped, or failed before treating evaOS review as settled for this head. provider_deferred means evaOS still intends to retry.

PR URL: #82

Details: Review failed; see bot evidence for operator-only details.

@github-actions

github-actions Bot commented Jul 13, 2026

Copy link
Copy Markdown

CI Report

All checks passed

Pipeline Status

Stage Status Details
✅ Typecheck success tsc --noEmit
✅ Tests success unit tests, 3 platforms
✅ E2E success gitnexus-web changes only

Test Results

Tests Passed Failed Skipped Duration
14685 14623 0 62 20s

✅ All 14623 tests passed

62 test(s) skipped — expand for details

Code Coverage

Tests

Metric Coverage Covered Base Delta Status
Statements 80.88% 54646/67561 N/A% 🟢 ████████████████░░░░
Branches 68.02% 33566/49345 N/A% 🟢 █████████████░░░░░░░
Functions 87.03% 6343/7288 N/A% 🟢 █████████████████░░░
Lines 84.4% 48759/57771 N/A% 🟢 ████████████████░░░░

📋 View full run · Generated by CI

@evaos-code-review-bot

evaos-code-review-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown

evaOS review status: stale head

PR: #82 - fix(vector): load extension before indexed embedding deletes
Head: e41431d92afe6afb48affa486995097907724395
Updated: 2026-07-13T19:31:30.902Z

evaOS review stopped because this queued head is no longer the live PR head.

Automation note: agents should wait for this comment to reach completed, stale_head, closed_or_merged_before_review, skipped, or failed before treating evaOS review as settled for this head. provider_deferred means evaOS still intends to retry.

PR URL: #82

Details: Superseded by a newer PR head.

@evaos-code-review-bot

evaos-code-review-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown

evaOS review status: completed

PR: #82 - fix(vector): load extension before indexed embedding deletes
Head: 6586cf464973df655a1429cc26989d06bd1a965c
Updated: 2026-07-13T20:45:16.947Z

evaOS review completed for this PR head.

Automation note: agents should wait for this comment to reach completed, stale_head, closed_or_merged_before_review, skipped, or failed before treating evaOS review as settled for this head. provider_deferred means evaOS still intends to retry.

PR URL: #82

Review URL: #82 (review)

@evaos-code-review-bot evaos-code-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Walkthrough

PR: #82 - fix(vector): load extension before indexed embedding deletes
Head: 6586cf464973df655a1429cc26989d06bd1a965c into reconcile/r18-vector-diagnostics. Review event: COMMENT.
Provider: GLM/Z.ai through ZCode (zcode-glm, zcode, model GLM-5.2).

Estimated review effort: 1/5 (~10 min)

Changed Files

File Status Churn Purpose Risk

Review Signal

No validated inline findings.
Dropped findings before posting: 0. High-severity findings: 0.

Risk Taxonomy

No finding categories.

Validation and Proof

1 required validation/proof recommendation(s) selected from changed files.

  • required: TypeScript/web build or CI proof - Runtime TypeScript/web files or package/config files changed. Proof: npm run build; typecheck; focused Vitest; green GitHub check.
    Proof status: sufficient - PR metadata mentions acceptable proof for each required validation recommendation.
    Profile validation hints: Call out stale index, wrong repo identity, memory growth, and destructive analyze behavior.
    Profile proof expectations: Look for focused CLI, index, query, or migration proof.

Related Context

Related issues/PRs: #81.
Suggested labels: none.
Suggested reviewers: none from current metadata.

Review Settings Preview

  • Profile: assertive
  • Enabled sections: Review summary (inline_review); Walkthrough (inline_review); Changed-files table (walkthrough); Effort estimate (walkthrough); Related issues/PRs (walkthrough); Suggested labels (suggestion_only); Review status comment (sticky_status)
  • Path instructions: none
  • Label suggestions: gitnexus, code-intelligence, backend
  • Reviewer suggestions: none
  • Suggestion behavior: suggestions only; labels and reviewers are not auto-applied.
  • Roadmap-only settings: auto-apply labels; auto-request reviewers; required status checks

Pre-merge checklist

  • Inline comments target current RIGHT-side diff lines.
  • No secret-like content survived into posted inline comments.
  • REQUEST_CHANGES is only used when eligible P0/P1 findings survive validation.
  • Required behavior proof is present or not applicable.
  • Labels and reviewers are suggestions only; the bot did not auto-apply them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant