-
-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panicked at 'called Option::unwrap()
on a None
value'
#303
Comments
Hi! Thanks for the bug report, a panic is definitely not something intended. I can't look into it right now, but just to put my mind at ease, can you check with just "git" and "nextcloud", or "jitsi" and "nextcloud"? To make sure it's due to the 3 arguments and not due to something weird with the nextcloud group in your setup. |
The queries work with the other two groups, there's nothing special about the While at it, thanks for this little gem, makes LDAP so easy :-) |
Alright, managed to reproduce it, it requires the exact structure you provided: |
I think I might have been misusing their API? It shouldn't have resulted in a panic anyway. I updated the code to use a more recent API (that incidentally I introduced in their code last year), and it should work now, I added a unit test to make sure. |
Alright, it should work in |
Thanks a lot for that quick fix! |
Query with two "OR" conditions works fine:
However, adding a third "OR" condition panics:
container log:
Version 0.4.0,
lldap:stable
image.The text was updated successfully, but these errors were encountered: