Skip to content

Stabilize Redis OOM CI check #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rblake2320 merged 1 commit into from
Jul 30, 2026
Merged

Stabilize Redis OOM CI check #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions redis-nonce-integration.mts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -375,11 +375,11 @@ try {
await establishContinuity(oomNamespace, 'epoch-before-oom');
const oomStore = await governed(redis, oomNamespace);
try {
const memoryInfo = await redis.info('memory');
const usedMatch = /^used_memory:(\d+)$/m.exec(memoryInfo);
if (!usedMatch) throw new Error('Redis INFO did not expose used_memory');
await redis.config('SET', 'maxmemory-policy', 'noeviction');
await redis.config('SET', 'maxmemory', String(Math.max(1, Number(usedMatch[1]) - 1)));
// A limit derived from an INFO snapshot is racy: Redis can reclaim memory
// before the authorization write and make a nominally over-limit write
// succeed. One byte is deterministically below the server's baseline.
await redis.config('SET', 'maxmemory', '1');

const oomRequest = requestFromHeaders(await client.signRequest('GET', '/api/data'));
const oomResult = await verifyBPCRequest(
Expand Down
Loading