Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Test failures with anyio 4.4.0 #1252

Closed
ianthomas23 opened this issue Jun 28, 2024 · 0 comments · Fixed by #1253
Closed

Test failures with anyio 4.4.0 #1252

ianthomas23 opened this issue Jun 28, 2024 · 0 comments · Fixed by #1253
Assignees
@ianthomas23
Labels
bug

Comments

@ianthomas23
Copy link
Collaborator

We are seeing test failures in CI when using anyio 4.4.0 which were OK with 4.3.0. Bisecting the anyio commits shows that the change in behaviour occurs at commit d3f38a7c which is PR agronholm/anyio#715. This emits a ResourceWarning for any MemoryObjectReceiveStream and MemoryObjectSendStream that are garbage collected before they are closed. The solution is to explicitly close the streams, I will submit a PR for this shortly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ianthomas23 ianthomas23

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Explicitly close memory object streams ipython/ipykernel
1 participant
@ianthomas23