Nathan Pastor

Looks like the stack trace is the same each time. With infinite stack trace, it looks like this: ``` Attempted to log "Error: wrapping the socket again!{} at wrapTcp (/Users/nathanpastor/code/gql-gateway/node_modules/dd-trace/packages/datadog-plugin-net/src/index.js:33:15)...

Actually wait, here's one from a different code path (looks like Jest teardown) ``` Attempted to log "Error: wrapping the socket again!{} at wrapTcp (/Users/nathanpastor/code/gql-gateway/node_modules/dd-trace/packages/datadog-plugin-net/src/index.js:33:15) at Socket.connectWithTrace (/Users/nathanpastor/code/gql-gateway/node_modules/dd-trace/packages/datadog-plugin-net/src/index.js:22:11) at /Users/nathanpastor/code/gql-gateway/node_modules/dd-trace/packages/dd-trace/src/scope/base.js:54:19...

Also not sure if it's helpful, but I get the same MaxListenersExceeededWarning when setting `DD_TRACE_DISABLED_PLUGINS=jest` (of course, without the stacktraces that have datadog-plugin-jest in them)

Thanks for the update @bengl . We will try the upgrade soon.

@bengl btw we tried the version upgrade, but ended up [here](https://github.com/DataDog/dd-trace-js/issues/2017) :(

This would be a great addition, I'm running into the same problem. I have to individually mock out `css` files in all tests. Was there a particular reason why only...

I second this :)

I would also be very interested in email notifications on game progress. I'm happy to contribute, if the maintainers are open to it? I have experience with email and push...

Ok, let me look around the code a bit and situate myself. I'll then outline an approach in this ticket, potentially incorporating another email service.

> Confirming that 2.2.0 is working, 2.2.1 is not Same here as well. Our builds are triggered from GitHub webhooks.