Skip to content

fix: raise the receiver memory limit to 512 MiB - #60

Merged
tbhb-agent merged 1 commit into
mainfrom
gm-mem512
Nov 15, 2026
Merged

tbhb-agent merged 1 commit into
mainfrom
gm-mem512

Conversation

@tbhb-agent

Copy link
Copy Markdown
Collaborator

Why

The receiver maps the store file into memory, and draining the queue pushes it near its 256 MiB limit. Hitting the limit would stop the process partway through the drain.

Behavior change

The receiver service limit in the Compose file rises from 256 MiB to 512 MiB. The host already runs at this value through a live update.

Verification

The deploy tests and the full Bazel run pass with the one-line change.

Opened-by: LLM effort=medium;harness=claude-code:2.1.325;model=anthropic:claude-sonnet-5-5;session=sha-256-64:6507fa80a17e0653;surface=cli
Generated-by: LLM effort=medium;harness=claude-code:2.1.325;model=anthropic:claude-sonnet-5-5;session=sha-256-64:6507fa80a17e0653;started_at=2026-11-15T17:24:44Z;surface=cli

Generated-by: LLM effort=medium;harness=claude-code:2.1.325;model=anthropic:claude-sonnet-5-5;session=sha-256-64:6507fa80a17e0653;started_at=2026-11-15T17:24:44Z;surface=cli
@tbhb-agent
tbhb-agent merged commit 91048ae into main Nov 15, 2026
8 checks passed
@tbhb-agent
tbhb-agent deleted the gm-mem512 branch November 15, 2026 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant