Skip to content

Close proxy dispatch classes on Client.close() - #826

Merged
lovelydinosaur merged 1 commit into
masterfrom
close-proxies
Feb 27, 2020
Merged

lovelydinosaur merged 1 commit into
masterfrom
close-proxies

Conversation

@lovelydinosaur

Copy link
Copy Markdown
Member

Closes #824

Actually it would be better for us to gracefully handle the case where one or more close() calls error, and still end up calling all of them, only raising an exception at the end, however there's no reason that we can treat that as an incremental improvement on top of this.

@lovelydinosaur lovelydinosaur added the bug Something isn't working label Feb 26, 2020
@lovelydinosaur lovelydinosaur mentioned this pull request Feb 27, 2020
3 tasks done

@florimondmanca florimondmanca left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@lovelydinosaur
lovelydinosaur merged commit 2714f32 into master Feb 27, 2020
@lovelydinosaur
lovelydinosaur deleted the close-proxies branch February 27, 2020 20:41
@lovelydinosaur lovelydinosaur mentioned this pull request Mar 5, 2020
Kludex referenced this pull request in pydantic/httpx2 May 11, 2026
…lled. (#826)

* Raise a neater RuntimeError when the correct async deps are not installed

* Run scripts/unasync

* Update CHANGELOG
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Development

Successfully merging this pull request may close these issues.

Too many open files if keep changing proxy

2 participants