fix: avoid "possible EventEmitter memory leak detected" warning - #6789
Merged
Conversation
🦋 Changeset detectedLatest commit: 7cec9a3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 26 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
n1ru4l
force-pushed
the
fix-max-listener-warning
branch
from
December 20, 2024 13:29
30026af to
cfab60c
Compare
Collaborator
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@graphql-tools/executor |
1.3.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-apollo-link |
1.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-envelop |
3.0.17-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-legacy-ws |
1.1.8-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-urql-exchange |
1.0.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/executor-yoga |
3.0.17-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/graphql-tag-pluck |
8.3.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
graphql-tools |
9.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/import |
7.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/links |
9.0.18-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/load |
8.0.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/apollo-engine-loader |
8.0.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/code-file-loader |
8.1.11-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/git-loader |
8.0.15-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/github-loader |
8.0.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/graphql-file-loader |
8.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/json-file-loader |
8.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/module-loader |
8.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/url-loader |
8.0.21-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/merge |
9.0.15-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/mock |
9.0.12-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/node-require |
7.0.10-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/relay-operation-optimizer |
7.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/resolvers-composition |
7.0.9-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/schema |
10.0.14-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
@graphql-tools/utils |
10.7.0-alpha-20241224080220-7cec9a36c8869567ca685def6970f80d29f8b7f5 |
npm ↗︎ unpkg ↗︎ |
dotansimha
approved these changes
Dec 23, 2024
ardatan
reviewed
Dec 23, 2024
Owner
|
See #6793
|
Contributor
💻 Website PreviewThe latest changes are available as preview in: https://7cd867a4.graphql-tools.pages.dev |
ardatan
reviewed
Dec 24, 2024
dotansimha
approved these changes
Dec 24, 2024
enisdenjo
approved these changes
Dec 24, 2024
|
FYI node 23.5.0 has this warning disabled for AbortSignal nodejs/node#55816. It's also scheduled to be in 22.13.0 with the backport already done nodejs/node@81c94a32e4 |
1 task
ardatan
added a commit
that referenced
this pull request
Sep 22, 2025
* fix: possible EventEmitter memory leak detected * Single place for AbortSignal listeners -> #6789 (#6793) * Single place for AbortSignal listeners * Fix * .. * Lets go * Small improvement * Changeset for utils * Update packages/executor/src/execution/__tests__/abort-signal.test.ts --------- Co-authored-by: Arda TANRIKULU <ardatanrikulu@gmail.com>
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.
Description
I noticed the "possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit." warning within our Hive GraphQL API service, which leads back to setting up too many event listeners here.
While the warning is not a real issue, we should avoid triggering it.
Extra from @ardatan ;
Type of change
How Has This Been Tested?
Existing tests pass, so the provided functionality stays the same.