Possible EventEmitter memory leak detected.

[lautarodragan]

stdout is showing the following message:

$ LOGGING_LEVEL=warn npm start

> @po.et/node@1.0.3 start /Projects/poet/node
> node dist/babel/src

Running Po.et Node

Loading Configuration...
Loaded configuration from .po.et/configuration.json
Switching to Structured Logging
Logging Level: warn

(node:28572) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
koa deprecated Support for generators will be removed in v3. See the documentation for examples of how to convert old middleware https://github.com/koajs/koa/blob/master/docs/migration.md dist/babel/src/API/Router.js:82:18
(node:28572) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit
(node:28572) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit
(node:28572) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit

This may not be a bug at all. Maybe we can try increasing the limit and seeing if the error message disappears.

[geoffturk]

@WesleyCharlesBlake Is this still showing up in the poet-node logs?

[WesleyCharlesBlake]

Yeah but only when logging at the info level

On Mon, 12 Nov 2018, 15:18 Geoff Turk, ***@***.***> wrote: @WesleyCharlesBlake <https://github.com/WesleyCharlesBlake> Is this still showing up in the poet-node logs? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#330 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHUCVKeJBZ2jcuZl_lH8fWrbKJM3RxOXks5uuXUcgaJpZM4V9DJM> .

-- Wesley Blake DevOps Engineer

[geoffturk]

@WesleyCharlesBlake And in prod?

[WesleyCharlesBlake]

@geoffturk yes still exists in prod

[geoffturk]

OK. It's in your backlog. Let's prioritize later.