-
Notifications
You must be signed in to change notification settings - Fork 231
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
Every new request opens new connection #570
Comments
This issue has had no activity in 90 days. Please comment if it is not actually stale |
bump |
Bump |
This issue has had no activity in 90 days. Please comment if it is not actually stale |
not stale |
This issue has had no activity in 90 days. Please comment if it is not actually stale |
Not fixed stupid bot |
Are you closing every issue which you cant implement within 90 days? Are you kidding me? Please fix it, with this huge performance penalty these api bindings are useless. |
This is supper inefficient. Please fix. We already have
api
object in the code with corresponding requests methods, so connection can be stored in the object.Upd:
With some monkey patching it can be fixed like this:
This way it works reliable and fast, without hitting azure DevOps rate-limiters due to multiple connections.
The text was updated successfully, but these errors were encountered: