MaxListenersExceededWarning about gauge HOT 4 CLOSED

Ah, that makes sense. I've got a patch for this and am meditating on how I want to test it, so it should land soonish. =)

from gauge.

Fixed in [email protected]! =)

from gauge.

Having more than one gauge at a time is pretty weird. What's your use case for that?

Currently the way it's written the expectation is that the onExit handler should exist as long as the gauge object does. As we have no way of knowing when a gauge object goes away, we have to hold on to it and it's going to be eternal.

I'm up for patching it so that it only keeps the onExit active as long as the gauge is enabled. This'd have the advantage of allowing disabled gauges to be garbage collected. Besides, having more than one gauge object enabled at a time is almost certainly an error as they'll write over each other. (If you have need of multiple gauges updating at once you're should be using gauge/plumbing and doing the screen updates yourself.)

from gauge.

@iarna Thanks for looking at this. :) Proposed patch sounds perfect.

It's not technically necessary to have them at the same time, which would be epilepsy-inducing, but merely instantiated in the same process over time. I encountered this in a CLI app that watches files and re-processes them, showing a new gauge each time. Upon the tenth file change it threw the above exit error. At no point was there more than one gauge visible, but their global event listeners were essentially leaking.

from gauge.