fix: raise default maxListeners to suppress benign gz stream warning#285
Merged
Conversation
Bun's internal fetch creates a zlib.Gunzip stream for gzip-compressed upstream responses. The Web Streams adapter + OpenCode's Effect-TS runtime attach 11 listeners (1 above the default limit of 10), triggering a one-time MaxListenersExceededWarning per process. Raise the process-wide default to 15 — still low enough to catch real leaks.
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
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.
Summary
events.defaultMaxListenersfrom 10 to 15 inpackages/gateway/instrument.tsto eliminate a benignMaxListenersExceededWarningthat fires once per OpenCode session.Root Cause
When the gateway runs in-process inside OpenCode (Bun), upstream
fetch()calls receive gzip-compressed responses. Bun's internal fetch creates azlib.Gunziptransform stream, and the Web Streams adapter + OpenCode's Effect-TS runtime attach 11 listeners to it — 1 above the default limit of 10.Logs confirm this is not a leak: exactly 1 warning per process (4 occurrences across 4 PIDs over a week), always exactly 11 listeners, never growing. All listeners are cleaned up when the response body is consumed.
Fix
Two lines at the top of
instrument.ts:15 is still low enough to catch real leaks (which grow to hundreds).