James Sumners

The `unbind()` will terminate the connection to the LDAP server. Therefore, no new messages will be received. What else should be done?

🤔 Likely a bug. If I'm not mistaken, there's an internal tracking of pending messages. This queue could be emptied in the `unbind` invocation prior to actually sending the unbind...

Please look at the `next` branch to determine if this issue is already resolved.

PRs are welcome.

It's possible I have it fixed in https://github.com/ldapjs/controls . I distinctly remember fixing something with the `BerWriter` not allowing empty values, but I cannot find where at the moment. But...

#383 is also a potential resolution.

Yeah, I thought I remembered a discussion. I agree at least for the connection events. But in this specific case, I think the ultimate solution is to remove the automatic...

The filter is processed at https://github.com/ldapjs/node-ldapjs/blob/d8c428f1d55eed3b96508bd84616550393336cd3/lib/client/client.js#L562 Which goes to https://github.com/ldapjs/node-ldapjs/blob/d8c428f1d55eed3b96508bd84616550393336cd3/lib/filters/index.js#L178-L184 I suspect this will solve your issue: ```js try { client.search(...) } catch (cause) { // deal with error }...

A PR is welcome.

An operation timeout of 10ms seems really short. The default is `Inifinity`. I would try a higher value. Also, specify a logger with the level at "trace" and provide the...