fix(memory): backfill provider.model in createWithAdapter when adapter returns empty string#95599
Conversation
|
Thanks for the context here. I swept through the related work, and this is now duplicate or superseded. Close as superseded: this branch is now a source-only duplicate of the older, open, maintainer-editable PR that carries the same Root-cause cluster Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. Canonical path: Keep #91660 as the canonical source-layer backfill candidate and leave the linked memory issue open until a fix merges. So I’m closing this here and keeping the remaining discussion on #91660. Review detailsBest possible solution: Keep #91660 as the canonical source-layer backfill candidate and leave the linked memory issue open until a fix merges. Do we have a high-confidence way to reproduce the issue? Yes. A high-confidence source reproduction exists: register a memory embedding adapter with a Is this the best way to solve the issue? The source-layer backfill is the best narrow fix, but this branch is not the best landing path because the older canonical PR carries the same change with tests and real behavior proof. Security review: Security review cleared: The diff only touches memory-core TypeScript and does not change workflows, dependencies, lockfiles, secrets, package metadata, or code-execution surfaces. AGENTS.md: found and applied where relevant. What I checked:
Likely related people:
Codex review notes: model internal, reasoning high; reviewed against 1cd6f81a46ae. |
|
Closing after 7 days with no review activity. This PR fixed empty model string causing search index identity corruption. Will re-open if reviewer feedback becomes available. |
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
…r returns empty string - Call resolveProviderModel once and reuse the resolved model - Backfill result.provider.model with resolvedModel when adapter returns an empty string, preventing a dirty search index identity Co-Authored-By: Claude <[email protected]> Signed-off-by: lsr911 <[email protected]>
9aa397e to
3dbbd79
Compare
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
@clawsweeper re-review |
|
@clawsweeper re-review |
|
Closing as superseded per ClawSweeper review — this fix is a duplicate of an older open PR. |
What Problem This Solves
Backfill
provider.modelwhen the adapter returns an empty string so callersalways see the resolved model name. An empty model string during boot can
overwrite a correct index identity and leave the search index permanently dirty.
Changes
resolveProviderModelonce and reuse the resolved modelresult.provider.modelwithresolvedModelwhen adapter returnsan empty string:
result.provider ? { ...result.provider, model: result.provider.model || resolvedModel } : nullEvidence
Before (empty model → dirty index)
After (model backfilled from resolved default)
AI-assisted.