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
{{ message }}
This repository was archived by the owner on May 14, 2024. It is now read-only.
When I try to use ldapjs client.unbind with node 10.0.0 (or 10.4.0) it does not work and the callback of unbind is never called. I debugged and it seems something in _sendSocket stops working, the function messageCallback is never called. While debugging it worked sometimes and the UnbindResponse was received successfully, but most of the time it didn't work, so I was wondering if it might be some timing issue, as while debugging everything runs slower/stepped.
client.search('ou=domain,dc=sub,dc=net',opts,(err,res)=>{if(err){cb(err,null);return;}res.on('searchEntry',entry=>{if(entry.object.hasOwnProperty('mail')){retrievedUsers[entry.object.uid]=entry.object;}});res.on('error',err=>{cb(err,null);client.unbind(err=>{if(err){logger.error(err);}});});res.on('end',()=>{client.unbind(err=>{// << --- never calledcb(err,retrievedUsers);});});});
When I try to use ldapjs
client.unbindwith node 10.0.0 (or 10.4.0) it does not work and the callback of unbind is never called. I debugged and it seems something in_sendSocketstops working, the functionmessageCallbackis never called. While debugging it worked sometimes and theUnbindResponsewas received successfully, but most of the time it didn't work, so I was wondering if it might be some timing issue, as while debugging everything runs slower/stepped.The last trace log I see is:
The code is