Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently had to connect a buildbot instance to an Active Directory and I needed a workaround to get it done, which I'd like to share. The problem is caused by Active Directory returning additional search result references which can not be suppressed by query parameters (e.g. https://superuser.com/questions/1438270/why-does-ad-return-searchresref-ldap-references-for-every-ldap-search). This leads to an exception when doing the user lookup.
I am sure that there are more elegant ways to filter out the unwanted search references than I did ;-) The unit tests ran fine without any changes before and after my change.
newsfragments
directory (and read theREADME.txt
in that directory)