Repository navigation
Conversation
Use the configured `STREAMS_MAX_LEN` value when creating the worker event stream instead of hardcoding a 50,000-entry limit.
BenHall-1
approved these changes
Oct 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RM-340
Description
The worker trimmed
stream:gateway-eventsto a hardcoded ~50000 entries. It now readsSTREAMS_MAX_LEN, which defaults to 50000, so behaviour is unchanged until it's set.This deliberately doesn't reuse
GATEWAY_STREAM_MAX_LEN: prod already sets that to 1000000 on the worker, so this merge would raise retention immediately. Before settingSTREAMS_MAX_LENhigher, check Redis memory and fix common/rpc acking with a cancelled context on shutdown. Otherwise XAUTOCLAIM replays messages that were already handled.Type of Change
Checklist