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
Inserting if (!context2) return cb(err, context2); before newContext = context2;improves the behaviour. But I am not sure about what it implies in terms of loopIndexVar increment.
The problem seems to happen in engine_utils.js within:
where
function(err, context2) {...}
is called with a null context and err set toError: socket hang up
and newContext.vars triggers an exceptionThe text was updated successfully, but these errors were encountered: