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 'entry', /ldap3/src/search.rs #45
Comments
If it can help, here is the expect that fail in my case :
The match_id(4) returns none since the id is 19. I'm not familiar enough with the ldap protocol to understand what is going on. Any idea ? |
It seems that entries return by stream.next() could be a referral. I'm not sure to know what is it and if it is normal to get, but I fixed my issue by adding this code before the
Do I have to write this condition or is it an issue in the lib ? I didn't have to do that with the previous version. |
It's documented in
So yes, filtering with |
Thank you for your help. Now, I have this panic : Everything works fine but I think it happens at then end of the connection. Why could I get this error, any idea ? Thanks again |
You shouldn't get a panic there. If it's reproducible, could you:
Alternatively or additionally, put a
on line 82 of If possible, open a separate issue for this, since it's unrelated to entry parsing. |
Sure, I will create a new issue for that and close that one. Thanks |
@fdubois1 I'm not reopening this, just a note that the latest alpha contains a workaround for non-filtered entries: search adapters which can be associated with a Search operation. The |
Great, thanks a lot for the information !! |
Hi,
I moved to the alpha version to use async/await. I kept my code almost the same except that now, I use LdapConnAsync and all async call.
I use streaming_search() in my code below and it panics with this :
panicked at 'entry', /opt/wayk/dev/ldap3/src/search.rs:148:13
The line who panic is SearchEntry::construct(entry). Any idea ?
Here is my code. The connection is already opened, I receive it in parameter.
Thank you in advance
The text was updated successfully, but these errors were encountered: