Closed zachowj closed 1 year ago
Fixed with release 1.18.2.
@zachowj With release 1.18.3 I did some further improvements by only registering for flows-started events if next event time option is activated (because the triggers are only needed in this case) and immediaterly unregistering the listener as soon as the event has been received.
Describe the bug Was looking into the cause of the below stack trace and noticed that the
flows:started
listener is not getting removed on node close.This is not the issue with the warning I am getting as I have over ten scheduler nodes in the workspace and each registers a new event listener going over the default max listener limit.
https://github.com/jensrossbach/node-red-contrib-chronos/blob/4faf519f1541667868cfb8c982e182ab41f1f47e/nodes/scheduler.js#L248
To reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Context information Please complete the following information.
Additional information Add any other information about the problem here.