openclaw/nix-openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/nix-openclaw.git synced 2026-07-25 05:35:30 -04:00
Code Issues 31 Packages Projects Releases Wiki Activity

Generated config contains invalid key: messages.queue.byProvider #5

New Issue
Closed
opened 2026-02-15 17:04:26 -05:00 by yindo · 1 comment
yindo commented 2026-02-15 17:04:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @schickling on GitHub (Jan 26, 2026).

Problem

The mkRoutingConfig function in the home-manager module generates a config with messages.queue.byProvider, but this key is not recognized by the clawdbot config schema.

Error

Invalid config at ~/.clawdbot/clawdbot.json:
- messages.queue: Unrecognized key: "byProvider"

Generated config

{
  "messages": {
    "queue": {
      "byProvider": {
        "discord": "queue",
        "telegram": "interrupt",
        "webchat": "queue"
      },
      "mode": "interrupt"
    }
  }
}

Impact

The clawdbot gateway fails to start because of this invalid config.

Suggested Fix

Either:

  1. Remove byProvider from mkRoutingConfig if it's not part of the schema
  2. Or update the clawdbot schema to accept this key

Workaround

Currently no easy workaround since configOverrides uses lib.recursiveUpdate which merges rather than replaces.

Originally created by @schickling on GitHub (Jan 26, 2026). ## Problem The `mkRoutingConfig` function in the home-manager module generates a config with `messages.queue.byProvider`, but this key is not recognized by the clawdbot config schema. ## Error ``` Invalid config at ~/.clawdbot/clawdbot.json: - messages.queue: Unrecognized key: "byProvider" ``` ## Generated config ```json { "messages": { "queue": { "byProvider": { "discord": "queue", "telegram": "interrupt", "webchat": "queue" }, "mode": "interrupt" } } } ``` ## Impact The clawdbot gateway fails to start because of this invalid config. ## Suggested Fix Either: 1. Remove `byProvider` from `mkRoutingConfig` if it's not part of the schema 2. Or update the clawdbot schema to accept this key ## Workaround Currently no easy workaround since `configOverrides` uses `lib.recursiveUpdate` which merges rather than replaces.
yindo closed this issue 2026-02-15 17:04:26 -05:00
yindo commented 2026-02-15 17:04:26 -05:00
Author
Owner
Copy Link
Copy Source

@joshp123 commented on GitHub (Feb 3, 2026):

[🤖 this message brought to you by codex] should be fixed in 952a04f3 (schema-only config + strip nulls). Closing for now — come and yell at me in #golden-path-deployments on discord if you're still having issues! Stability work continues; we are making this better every week.

@joshp123 commented on GitHub (Feb 3, 2026): [🤖 this message brought to you by codex] should be fixed in 952a04f3 (schema-only config + strip nulls). Closing for now — come and yell at me in #golden-path-deployments on discord if you're still having issues! Stability work continues; we are making this better every week.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
maintainer-roadmap
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/nix-openclaw#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?