Nested event listeners break currentContext

[vctandrade]

const eventContext = require('event-context')
const eventContextPluginNode = require('event-context-plugin-node')
const EventEmitter = require('events').EventEmitter

eventContextPluginNode.patch()

let ctx = eventContext.createContext()
let emitter = new EventEmitter()

assert(eventContext.getCurrentContext() === null)  // passes

ctx.run(function() {
  emitter.on('A', function() {
    emitter.on('B', function() {})
    emitter.emit('B')
  })
})
emitter.emit('A')

assert(eventContext.getCurrentContext() === null)  // fails

[tungv]

the first eventContext.getCurrentContext() should not be null. It's a bug. I don't think it has anything to do with nested event handler

[vctandrade]

Should it not? I thought currentContext was only set when you called ctx.run, and then reverted right after its execution.

Even so, there does seem to be some unexpected behaviours regarding the EventEmitter patch. Because of its synchronous implementation, when emitter.emit is called, the handler functions act within the scope of the current context, which is pushed to previousContext.

If this happens multiple times, the previousContext is overridden and lost. Then, on the way back, revertContext happens multiple times as well, restoring the wrong context.