You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per description, setting batchInterval causes my node.js process to hang even though it's reached its end. The reason being is the interval timer in the underlying splunk logger is not being cleared. I think the solution is to listen to the stream's end event, flush and clear the interval timer.
Platform version: OS X 10.11.6
Framework version: v4.6.0
Environment: local
Versions:
As per description, setting batchInterval causes my node.js process to hang even though it's reached its end. The reason being is the interval timer in the underlying splunk logger is not being cleared. I think the solution is to listen to the stream's end event, flush and clear the interval timer.
Platform version: OS X 10.11.6
Framework version: v4.6.0
Environment: local
Versions:
The text was updated successfully, but these errors were encountered: