Schema Validation Bug Report

[austinlaw076]

Plugin Version

1.1.0-beta.9

OpenClaw Version

2026.4.5

Bug Description

memory-lancedb-pro-schema-bug-report.md

memory-lancedb-pro invalid config: embedding: must have required property 'embedding'

This error repeats every 2 seconds, causing high CPU usage (~100% on one core).

### Expected Behavior


- Plugin should only be validated when it has a config entry in `plugins.entries`
- Or the validation error should not repeat in a loop
- Ideally, the error message should clearly indicate what's wrong with the config

### Steps to Reproduce

1. Install memory-lancedb-pro to OpenClaw extensions:
   ```bash
   openclaw plugins install --link ~/.openclaw/node_modules/memory-lancedb-pro

Or manually copy to ~/.openclaw/extensions/memory-lancedb-pro/

2. Observe the gateway logs - the error repeats:

   [plugins] memory-lancedb-pro invalid config: embedding: must have required property 'embedding'
   

3. This causes ~100% CPU usage on one core due to the validation loop

Error Logs / Screenshots

The `configSchema` in `openclaw.plugin.json` is:

{
  "configSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {
      "embedding": {
        "type": "object",
        "additionalProperties": false,
        "properties": {...},
        "required": ["apiKey"]
      },
      ...
    },
    "required": ["embedding"]
  }
}


When validated locally with AJV using the config `{ embedding: {...} }`, it passes. But OpenClaw seems to be validating differently, possibly passing a nested structure or different format.

Embedding Provider

None

OS / Platform

Ubuntu 25.10

[AliceLJY]

Thanks for reporting — this is the same schema validation issue tracked in #554 and related to #556.

The root cause is how OpenClaw validates plugin configs against configSchema. The "required": ["embedding"] at the top level of the schema means the gateway rejects configs that don't include an embedding key at the level it expects. This interacts with how OpenClaw wraps/unwraps plugin config sections before validation.

The repeated validation loop (causing 100% CPU) is a separate concern worth flagging — even if the config is invalid, the plugin shouldn't retry validation in a tight loop.

Tracking the fix in #554. Will close this as duplicate if you agree.