Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Summary
Keep open: current main still declares the LanceDB plugin without the apache-arrow peer that the locked @lancedb/lancedb package requires, and the ltm CLI path reaches that runtime dependency through the plugin.

Reproducibility: no. live high-confidence CLI reproduction was established in this read-only checkout. Source inspection still gives a clear reproduction path: openclaw ltm loads the plugin runtime, the plugin imports @lancedb/lancedb, and the package metadata omits that dependency's required apache-arrow peer.

Next step
This is a narrow plugin packaging bug with clear likely files and validation, but it still needs live/package-path reproduction before treating the fix as fully proven.

Review details

Best possible solution:

Keep the fix inside memory-lancedb packaging and contract coverage so @lancedb/lancedb always has its required Arrow peer without moving LanceDB ownership into core.

Do we have a high-confidence way to reproduce the issue?

No live high-confidence CLI reproduction was established in this read-only checkout. Source inspection still gives a clear reproduction path: openclaw ltm loads the plugin runtime, the plugin imports @lancedb/lancedb, and the package metadata omits that dependency's required apache-arrow peer.

Is this the best way to solve the issue?

Yes, the narrow maintainable fix is to declare and test the missing plugin-owned runtime dependency. Core Gateway memory behavior should stay unchanged unless package validation shows a shared dependency-contract gap.

Acceptance criteria:

pnpm test src/plugins/contracts/package-manifest.contract.test.ts src/plugins/contracts/extension-runtime-dependencies.contract.test.ts extensions/memory-lancedb/index.test.ts
pnpm check:changed

What I checked:

Issue report: The reporter says openclaw ltm hangs because bundled memory-lancedb is missing apache-arrow, while the Gateway memory system works. (62fb50d7fc5d)
Plugin dependency manifest: memory-lancedb declares @lancedb/lancedb, openai, and typebox, but not apache-arrow. (extensions/memory-lancedb/package.json:10, 62fb50d7fc5d)
Upstream dependency contract from lockfile: The lockfile records @lancedb/lancedb@0.27.2 with peer dependency apache-arrow: >=15.0.0 <=18.1.0 and resolves it with apache-arrow@18.1.0 in the workspace. (pnpm-lock.yaml:2785, 62fb50d7fc5d)
CLI surface reaches LanceDB runtime: The plugin registers the ltm command and the command handlers call the LanceDB-backed db object for list/search/query/stats. (extensions/memory-lancedb/index.ts:835, 62fb50d7fc5d)
Existing contract gap: The package manifest contract lists only @lancedb/lancedb as a memory-lancedb local runtime dependency, so the current guard does not require the transitive peer to be declared by the plugin package. (src/plugins/contracts/package-manifest.contract.test.ts:46, 62fb50d7fc5d)
History routing: Current blame/log for the dependency manifest and runtime loader points to commit 99176e1 on current main. (extensions/memory-lancedb/package.json:10, 99176e1950e2)

Likely related people:

Peter Steinberger: Current blame and git log -S point to the dependency declaration and LanceDB runtime loader being introduced in commit 99176e1. (role: introduced current manifest/runtime surface; confidence: high; commits: 99176e1950e2; files: extensions/memory-lancedb/package.json, extensions/memory-lancedb/lancedb-runtime.ts, extensions/memory-lancedb/index.ts)
Gustavo Madeira Santana: Recent history includes memory-lancedb migration work to scoped plugin SDK imports, so this person is likely familiar with the plugin boundary and packaging surface. (role: adjacent memory-lancedb maintainer; confidence: medium; commits: 6b19b7f37af3, 1278ee924803; files: extensions/memory-lancedb/index.ts)
LUKSOAgent: The changelog credits this handle for prior memory-lancedb runtime dependency manifest lookup work that fixed missing @lancedb/lancedb dependency errors. (role: prior dependency-resolution contributor; confidence: medium; files: CHANGELOG.md)

Remaining risk / open question:

I did not run openclaw ltm because this review was read-only and the checkout has no installed dependencies, so the exact hang versus immediate import failure still needs focused reproduction in the fix PR.
The repair should verify the packaged/externalized plugin install path, because peer auto-install behavior may differ across npm, pnpm, and bundled plugin flows.
Adding apache-arrow directly will likely require aligning package-manifest and runtime-dependency contract tests so the new indirect runtime dependency is intentional.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 62fb50d7fc5d.

Uh oh!

[memory-lancedb] CLI openclaw ltm hangs - missing apache-arrow in bundled plugin #76910

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions