-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
Runaway loop, never returns #16
Comments
Thanks for your comments! The loop in What you're probably seeing is an artifact of the very large If the loop exited early, consumers of exchangelib that don't implement their own rate-limiting code could quickly swamp such a server with new requests. That would only make things worse. Instead, it's better if the request loop waits patiently until the server is functioning again. If the connecting user has hit a throttling policy, then the server will only respond with a HTTP 401, as if the password is wrong. The only cure is to stop making requests. There is no other indication AFAIK, so the code can't distinguish between the two situations. Anyway, I'd be happy for any contributions to the project! |
Please re-open if you still think this is a bug. |
I have an Exchange server with misconfigured autodiscover (doesn't return a good response), and your autodiscover never returns, it just runs forever (see more below)... I have been writing Exchange code for Python for a couple of years, and I'd be happy to join your project and then I could fix issues like this.
I found the issue in your code:
util.py line 253
You are using a "while True:" loop, which is dangerous in Python, I had some similar issues with my project. I recommend you put in some type of limit like:
The text was updated successfully, but these errors were encountered: