refactor: Switch from ldap_poller to a direct implementation #106
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.
This cuts out an incredible amount of middle-man code that is completely unnecessary for famedly-sync in practice.
Also cleans up a couple of inherited bugs (like not correctly quitting if we run into a connection issue), and hopefully increases logging capacity. Basically, a prerequisite of famedly/ldap-poller#36, since this lets us reasonably fix the issue downstream.
TODO:
sync
bits with async codeldap3
created a sync interface by just callingblock_on
-type things on their async methods, so it is completely incompatible with otherwise async code