Skip to content

memory-lancedb 2026.6.1 fails to install: apache-arrow 21.1.0 conflicts with @lancedb/lancedb 0.30.0 peer range #90295

Closed

Description

@allenhurff

Summary

After upgrading OpenClaw from 2026.5.28 to 2026.6.1, the @openclaw/memory-lancedb@2026.6.1 plugin update fails during dependency installation and OpenClaw disables the plugin.

This appears to be a package dependency mismatch in the 2026.6.1 memory-lancedb bundle, not LanceDB data corruption.

Environment

  • OpenClaw before upgrade: 2026.5.28
  • OpenClaw after upgrade: 2026.6.1 (2e08f0f)
  • macOS: 26.5 arm64
  • Node: 24.14.1
  • npm: 11.11.0
  • Install type: npm
  • Plugin being updated: clawhub:@openclaw/memory-lancedb

Failure

openclaw update / openclaw plugins update memory-lancedb fails with npm ERESOLVE:

Failed to update memory-lancedb: npm install failed: npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @openclaw/memory-lancedb@2026.6.1
npm error Found: apache-arrow@21.1.0
npm error node_modules/apache-arrow
npm error apache-arrow@"21.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer apache-arrow@">=15.0.0 <=18.1.0" from @lancedb/lancedb@0.30.0
npm error node_modules/@lancedb/lancedb
npm error @lancedb/lancedb@"0.30.0" from the root project

Observed Result

  • Core OpenClaw upgrade succeeds.
  • memory-lancedb update fails.
  • OpenClaw disables memory-lancedb in config.
  • Memory slot falls back to memory-core.
  • Repeated config warning appears:
plugins.entries.memory-lancedb: plugin disabled (disabled in config) but config is present

The previous memory-lancedb@2026.5.28 extension remains physically installed and the LanceDB store is still readable.

Expected Result

@openclaw/memory-lancedb@2026.6.1 should install cleanly under npm 11, or its package dependencies should align with the peer dependency declared by @lancedb/lancedb@0.30.0.

Specifically, either:

  • do not require apache-arrow@21.1.0 while using @lancedb/lancedb@0.30.0, or
  • update the LanceDB dependency to a version whose peer range accepts Arrow 21, if such a version exists, or
  • pin Arrow inside the accepted peer range.

Local Data Check

The LanceDB data itself appears intact. A local coverage audit against the existing store passed after the failed update:

ok=true
lancedb_total=9065
lancedb_lcm_sync=9060
ledger_rows=9060

Workaround Used Locally

I am temporarily restoring the previous active memory posture by re-enabling the still-installed memory-lancedb@2026.5.28 plugin in config, rather than forcing npm with --force or --legacy-peer-deps.

Activity

  1. clawsweeper commented on Jun 4, 2026

    @clawsweeper
    Contributor

    Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 21, 2026, 1:50 PM ET / 17:50 UTC.

    Summary
    Keep open: current main, the latest release, and the currently published memory-lancedb package still carry the Arrow/LanceDB peer mismatch, while the linked repair PR is open and conflicting rather than merged.

    Reproducibility: yes. Source, shrinkwrap, root lockfile, release tag, and live npm registry metadata show Arrow 21.1.0 outside LanceDB 0.30.0's accepted peer range; I did not run an install in this read-only review.

    Root-cause cluster
    Relationship: canonical
    Canonical: #90295
    Summary: This issue is the canonical same-repository report for the memory-lancedb Arrow/LanceDB peer mismatch; one duplicate is closed and one open PR is the fix candidate.

    Members:

    Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

    Next step
    No new issue-derived fix PR should be queued because the open linked PR already owns the implementation path.

    Review details

    Best possible solution:

    Land #90407 after trusted dependency-graph review, or apply the equivalent manifest, shrinkwrap, and lockfile repair from a maintainer branch and publish a fixed memory-lancedb package.

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

    Yes. Source, shrinkwrap, root lockfile, release tag, and live npm registry metadata show Arrow 21.1.0 outside LanceDB 0.30.0's accepted peer range; I did not run an install in this read-only review.

    Is this the best way to solve the issue?

    Yes. A narrow plugin-owned dependency graph alignment is the best fix; forcing npm peer resolution or adding runtime fallback would not repair the published package contract.

    AGENTS.md: found and applied where relevant.

    Remaining risk / open question:

    • The latest published memory-lancedb package still contains the mismatched dependency pair, so users updating that official memory plugin can continue to hit npm ERESOLVE.
    • The open fix path requires conflict refresh plus trusted dependency-graph review or an equivalent maintainer-applied package graph repair before it can land and ship.

    Codex review notes: model internal, reasoning high; reviewed against eea777c9fc9c.

    Label changes

    Label justifications:

    • P2: This breaks install/update for one official memory plugin while core OpenClaw remains usable with the fallback memory path.
    • impact:session-state: The failed update disables or displaces the configured LanceDB memory plugin, changing active memory and context behavior for affected users.
    Evidence reviewed

    What I checked:

    • Current main manifest mismatch: Current main declares @lancedb/lancedb 0.30.0 together with apache-arrow 21.1.0 in the memory-lancedb package manifest. (extensions/memory-lancedb/package.json:11, eea777c9fc9c)
    • Current shrinkwrap records the conflicting peer range: The plugin shrinkwrap root depends on apache-arrow 21.1.0 while the @lancedb/lancedb entry declares peerDependencies.apache-arrow as >=15.0.0 <=18.1.0. (extensions/memory-lancedb/npm-shrinkwrap.json:11, eea777c9fc9c)
    • Root lockfile has the same resolved mismatch: The root lockfile resolves @lancedb/lancedb@0.30.0(apache-arrow@21.1.0) and records the same apache-arrow peer ceiling of <=18.1.0. (pnpm-lock.yaml:1043, eea777c9fc9c)
    • Live LanceDB package contract: npm registry metadata for @lancedb/lancedb@0.30.0 reports peerDependencies.apache-arrow as >=15.0.0 <=18.1.0.
    • Latest published memory-lancedb still affected: npm registry metadata for @openclaw/memory-lancedb@latest reports version 2026.6.9 with apache-arrow 21.1.0 and @lancedb/lancedb 0.30.0.
    • Latest release still contains the mismatch: Release v2026.6.9 was published on 2026-06-21 and its tag content still declares the same memory-lancedb dependency pair. (extensions/memory-lancedb/package.json:11, c645ec4555c0)

    Likely related people:

    • steipete: Commit 48ccc50 moved memory-lancedb to @lancedb/lancedb 0.30.0 and apache-arrow 21.1.0 in the package manifest, shrinkwrap, and root lockfile. (role: introduced dependency pair; confidence: high; commits: 48ccc50282eb; files: extensions/memory-lancedb/package.json, extensions/memory-lancedb/npm-shrinkwrap.json, pnpm-lock.yaml)
    • vincentkoc: Recent current-main and release commits still touch the memory-lancedb package graph and carry the affected dependency pair into the latest release train. (role: recent package graph and release contributor; confidence: medium; commits: 9f888d95e082, c645ec4555c0; files: extensions/memory-lancedb/package.json, extensions/memory-lancedb/npm-shrinkwrap.json, pnpm-lock.yaml)
    • amittell: Recent memory-lancedb runtime work makes this a useful routing signal for validating plugin behavior after the package graph repair lands. (role: recent adjacent runtime contributor; confidence: medium; commits: 945faf8e6798; files: extensions/memory-lancedb/index.ts, extensions/memory-lancedb/index.test.ts)
    • sahibzada-allahyar: The open linked PR changes the manifest, shrinkwrap, and root lockfile toward apache-arrow 18.1.0 for this issue. (role: open fix PR author; confidence: medium; commits: f4fea32b3def; files: extensions/memory-lancedb/package.json, extensions/memory-lancedb/npm-shrinkwrap.json, pnpm-lock.yaml)
    How this review workflow works
    • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
    • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
    • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
    • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
    • Maintainers can also comment @clawsweeper review to request a fresh review only.
    • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
    • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
    • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.
  2. added
    P2Normal backlog priority with limited blast radius.
    impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.
    issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.
    clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.
    clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    on Jun 4, 2026
  3. added
    clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    and removed
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.
    on Jun 15, 2026
  4. allenhurff commented on Jun 21, 2026

    @allenhurff
    ContributorAuthor

    Hey maintainers,

    Following up with current user-impact context and linking the open fix path: PR #90407 (#90407) is still the clean/minimal fix candidate for this issue.

    As of today, the latest published @openclaw/memory-lancedb is 2026.6.9, and it still declares:

    • @lancedb/lancedb@0.30.0
    • apache-arrow@21.1.0

    But @lancedb/lancedb@0.30.0 still peers apache-arrow >=15.0.0 <=18.1.0, so standard npm 11 resolution remains broken.

    This has now hit me across four consecutive OpenClaw updates, including 2026.6.9. My local repair path continues to restore the memory-lancedb@2026.5.28 pin and keep LanceDB memory healthy, but that is now a recurring manual workaround for what feels like a core memory-stack component.

    The linked PR already makes the package-contract repair by pinning Arrow to 18.1.0 and regenerating the graph files. From the latest review, the remaining path looks like either:

    1. refresh/rebase PR fix(memory-lancedb): align apache arrow peer dependency #90407 if needed, review the resolved dependency graph, and authorize the exact refreshed head SHA through the dependency guard, or
    2. have maintainers/secops apply the equivalent one-line dependency repair internally from a trusted branch and publish a repaired memory-lancedb@2026.6.x.

    Happy to provide any extra logs or test a fixed package immediately after it is published. Thanks.

  5. locked as resolved and limited conversation to collaborators on Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions