-
Notifications
You must be signed in to change notification settings - Fork 305
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
Anyio version 3 breaks AsyncContentsManager #487
Comments
Hi @kevin-bates ! thanks for the detailed bug report. I can take a look and try to get a fix out end of this week. Is that ok? |
No worries. The dependency is capped so we're good right now. Whenever you can poke at this is fine - thank you! |
Hi @kevin-bates, I looked into this a bit today, and it seems like there could be a bug in anyio, so I created a github issue for that and proposed a fix. I hope we get an answer soon! |
Description
Anyio version 3 was recently introduced and we found that the various AsyncContentsManager calls that use anyio's
run_sync_in_worker_thread
method fail with a traceback similar to:The failure was also seen on a build of PR 483 prior to capping
anyio < 3
.Reproduce
anyio
version 3 is installed (released on April 20)pytest -v jupyter_server/tests/services/contents/test_largefilemanager.py::test_save
Expected behavior
Tests should pass.
Context
I noticed the following deprecation warning when running
pytest
:However, a quick attempt to switch to
anyio.to_thread.run_sync()
resulted in the same issue since it appearsrun_sync()
still callsrun_sync_in_worker_thread()
internally. As a result, this may be ananyio
issue.Using run_sync()
cc: @mwakaba2
The text was updated successfully, but these errors were encountered: