lbug npm package: All extensions fail to load with ABI mismatch (undefined symbol)

[arimxyer]

Summary

The lbug npm package cannot load any extensions due to ABI mismatch between the npm package and the extension binaries served by the extension server.

Environment

• Package: lbug (npm)
• Versions tested: 0.12.0, 0.12.2, 0.13.0, 0.13.1-dev.18, 0.13.2-dev.4
• Platform: Linux x64 (tested in Docker with Bun 1.3.5, and locally with Node.js)
• Extension server: Default (extensions download to ~/.lbug/extension/dev/linux_amd64/)

Steps to Reproduce

const lbug = require('lbug');

async function test() {
  const db = new lbug.Database('./test.db');
  await db.init();
  const conn = new lbug.Connection(db);
  
  // Check pre-loaded extensions
  const loaded = await conn.query('CALL show_loaded_extensions() RETURN *');
  console.log('Pre-loaded:', loaded.getAllSync()); // Returns []
  
  // Try to load extension
  await conn.query('INSTALL vector');  // OK
  await conn.query('LOAD vector');     // FAILS
}
test();

Expected Behavior

Per the documentation at https://docs.ladybugdb.com/extensions:

"If you've upgraded to the latest version v0.11.3, Ladybug has pre-installed and pre-loaded four commonly used extensions (algo, fts, json, vector) for you. You do not need to manually INSTALL or LOAD these extensions."

Extensions should either be pre-loaded, or INSTALL + LOAD should work.

Actual Behavior

1. show_loaded_extensions() returns empty array - extensions are NOT pre-loaded
2. LOAD vector (without INSTALL) fails: "Extension has not been installed"
3. INSTALL vector succeeds (downloads file)
4. LOAD vector (after INSTALL) fails with ABI mismatch:

IO exception: Failed to load library: /root/.lbug/extension/dev/linux_amd64/vector/libvector.lbug_extension 
which is needed by extension: vector.
Error: undefined symbol: _ZTIN4lbug7catalog12IndexAuxInfoE

All four extensions fail identically: vector, fts, json, algo

Analysis

The error undefined symbol: _ZTIN4lbug7catalog12IndexAuxInfoE (demangled: typeinfo for lbug::catalog::IndexAuxInfo) indicates the extension binaries were compiled against a different version of the core library than what's shipped in the npm package.

Notable observations:

• Extensions download to /dev/ path even for non-dev npm versions
• The upstream kuzu npm package (v0.11.3) has these extensions statically linked and works perfectly
• The lbug npm package starts at v0.12.0 (no 0.11.x exists), but docs reference v0.11.3

Comparison with Kuzu

const kuzu = require('kuzu'); // v0.11.3

// show_loaded_extensions() returns:
// ALGO, FTS, JSON, VECTOR - all with source "STATIC LINK"

// Vector index creation works immediately, no INSTALL/LOAD needed

Suggested Fix

Either:

1. Statically link extensions into the npm package (like upstream Kuzu does)
2. Ensure extension server binaries match the exact ABI of each npm release
3. Update documentation to reflect actual npm package behavior

Workaround

Use upstream kuzu npm package instead of lbug.

[adsharma]

This is a known issue with v0.13.0. Release v0.13.1 fixed it, but looks like npm packages didn't get uploaded.
Kicked off a build+deploy job here:

https://github.com/LadybugDB/ladybug/actions/runs/20758162184

[adsharma]

Please test v0.13.1 https://www.npmjs.com/package/lbug

[arimxyer]

sounds good, I'll reply back when I get to retest it and let you know. I also see 14 went out as well, congrats to that!

[mattijsdp]

I think I'm facing the same issue, tried 0.14.0 and 0.14.1 but still can't get it to work.

Failed to load FTS extension. Full-text search will not be available: IO exception: Failed to load library: /root/.lbug/extension/0.14.0/linux_amd64/fts/libfts.lbug_extension which is needed by extension: fts.
Error: /root/.lbug/extension/0.14.0/linux_amd64/fts/libfts.lbug_extension: undefined symbol: _ZTIN4lbug7catalog12IndexAuxInfoE.

[adsharma]

The problem with v0.14.0 is known. But I expect v0.14.1 to work. Can you rm the .lbug/extension and retry?

[adsharma]

$ lbug --version
Lbug 0.14.1
$ lbug
Opening the database under in-memory mode.
Enter ":help" for usage hints.
lbug> install fts;
┌──────────────────────────────────────────────────────────────────────────┐
│ result                                                                   │
│ STRING                                                                   │
├──────────────────────────────────────────────────────────────────────────┤
│ Extension: fts installed from the repo: http://extension.ladybugdb.com/. │
└──────────────────────────────────────────────────────────────────────────┘
(1 tuple)
(1 column)
Time: 2.99ms (compiling), 686.24ms (executing)
lbug> load fts;
┌─────────────────────────────────┐
│ result                          │
│ STRING                          │
├─────────────────────────────────┤
│ Extension: fts has been loaded. │
└─────────────────────────────────┘
(1 tuple)
(1 column)
Time: 0.21ms (compiling), 4.39ms (executing)
lbug> call show_loaded_extensions() return *;
┌────────────────┬──────────────────┬─────────────────────────────────────────────────────────────────────────────────┐
│ extension name │ extension source │ extension path                                                                  │
│ STRING         │ STRING           │ STRING                                                                          │
├────────────────┼──────────────────┼─────────────────────────────────────────────────────────────────────────────────┤
│ FTS            │ OFFICIAL         │ /home/ubuntu/.lbug/extension/0.14.0/linux_amd64/fts/libfts.lbug_extension       │
│ VECTOR         │ OFFICIAL         │ /home/ubuntu/.lbug/extension/0.14.0/linux_amd64/vector/libvector.lbug_extension │
└────────────────┴──────────────────┴─────────────────────────────────────────────────────────────────────────────────┘

It's expected that v0.14.1 binaries use v0.14.0 extensions. I didn't rebuild the extensions since it's not necessary.

[adsharma]

Also tested via: https://gist.github.com/adsharma/7972bc2db380000ab7f514d1d3083a3a

[mattijsdp]

I retried, here is a reproducible example which hopefully helps. Let me know if I'm doing something wrong.

Dockerfile:

FROM ubuntu:24.04

RUN apt-get update && apt-get install -y curl unzip && \
    curl -fsSL https://bun.sh/install | bash -s "bun-v1.3.3" && \
    ln -s /root/.bun/bin/bun /usr/local/bin/bun && \
    apt-get clean && rm -rf /var/lib/apt/lists/*

WORKDIR /app

RUN echo '{"dependencies":{"lbug":"0.14.1"},"trustedDependencies":["lbug"]}' > package.json && bun install

COPY test.ts .

CMD ["bun", "run", "test.ts"]

test.ts:

import lbug from "lbug";
import { existsSync, rmSync } from "node:fs";

const dbPath = "/tmp/test.kuzu";
if (existsSync(dbPath)) rmSync(dbPath, { recursive: true });

console.log("lbug version:", lbug.VERSION);

const db = new lbug.Database(dbPath);
const conn = new lbug.Connection(db);

await conn.query("INSTALL FTS;");
console.log("FTS installed");

await conn.query("LOAD EXTENSION FTS;");
console.log("FTS loaded");

conn.close();

Error:

lbug version: 0.14.1
FTS installed
error: IO exception: Failed to load library: /root/.lbug/extension/0.14.0/linux_arm64/fts/libfts.lbug_extension which is needed by extension: fts.
Error: /root/.lbug/extension/0.14.0/linux_arm64/fts/libfts.lbug_extension: undefined symbol: _ZTIN4lbug7catalog12IndexAuxInfoE.

Bun v1.3.3 (Linux arm64)

I am out of my depth here but fwiw, this is Opus view:

ABI Mismatch:
When a shared library (.so/.dylib/extension) was compiled against version A of a dependency but loaded at runtime with version B, the binary layouts may differ. The error:
undefined symbol: _ZTIN4lbug7catalog12IndexAuxInfoE
This is a C++ mangled symbol for typeinfo for lbug::catalog::IndexAuxInfo. The extension was compiled expecting this class to exist (likely in lbug 0.14.0), but in lbug 0.14.1, this class was renamed, removed, or changed.

[adsharma]

Thanks for testing. My read is that this is a bun specific issue fixed by the PR above. Will make a v0.14.2 release so you can test.

[adsharma]

Still failing after v0.14.2 release.

[aheev]

Thanks for testing. My read is that this is a bun specific issue fixed by the PR above. Will make a v0.14.2 release so you can test.

Yes — it’s a Bun issue. I’ve raised it with them here: oven-sh/bun#26137

workaround: LD_PRELOAD=$(find node_modules -name lbugjs.node | head -n 1) bun run test.ts

[mattijsdp]

Thanks for the workaround!