This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
Suppress web3 MaxListenersExceededWarning #1088
Merged
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.
Suggests this isn't obviously the result of negligence cleaning up emitters here. Also not proof of a lack of negligence, although have tried hard not to neglect this.
Also looks like it's not possible to manually set these limits on the PromiEvent since that part of the EventEmitter interface isn't exposed.
Warning looks like this:
(node:60858) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 data listeners added. Use emitter.setMaxListeners() to increase limit
Believe this will also need to be done for the console/develop but a different approach might be possible there. Mocha implements it's
--no-warnings
option by passing it as node flag to the process when they shell out.