HKUDS/nanobot · error · ValueError
group_message_buffer_size must be > 0
Error message
group_message_buffer_size must be > 0
What it means
Error "group_message_buffer_size must be > 0" thrown in HKUDS/nanobot.
Source
Thrown at nanobot/channels/signal/runtime.py:339
enabled: bool = False
phone_number: str = "" # Your Signal phone number (e.g., "+1234567890")
daemon_host: str = "localhost"
daemon_port: int = 8080
group_message_buffer_size: int = 20 # Number of recent group messages to keep for context
# Override the directory signal-cli writes inbound attachments to. When
# None, defaults to ~/.local/share/signal-cli/attachments (the daemon's
# platform default on Linux). Set this if the daemon is running with a
# custom XDG_DATA_HOME or on macOS/Windows where the default path differs.
attachments_dir: str | None = None
dm: SignalDMConfig = Field(default_factory=SignalDMConfig)
group: SignalGroupConfig = Field(default_factory=SignalGroupConfig)
@field_validator("group_message_buffer_size")
@classmethod
def _validate_buffer_size(cls, v: int) -> int:
if v <= 0:
raise ValueError("group_message_buffer_size must be > 0")
return v
@computed_field # type: ignore[prop-decorator]
@property
def allow_from(self) -> list[str]:
"""Aggregate allowlist for the base-class is_allowed() check.
Returns the union of dm.allow_from and group.allow_from so the base
channel gate sees a populated list when either sub-policy is configured.
A ``"*"`` wildcard in either sub-list propagates to allow all.
"""
return list(dict.fromkeys(self.dm.allow_from + self.group.allow_from))
class SignalChannel(BaseChannel):
"""
Signal channel using signal-cli daemon via HTTP JSON-RPC interface.
View on GitHub (pinned to 42f37dc4c0)
When it happens
Trigger: Thrown at nanobot/channels/signal/runtime.py:339 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of HKUDS/nanobot@42f37dc4c0 (2026-08-26).
Data as JSON: /api/errors/08d97a3d750d3fa0.
Report an issue: GitHub.