Joongi Kim

I just hit [a similar problem regarding contextvars with async-yield fixtures](https://aio-libs.discourse.group/t/contextvars-with-pytest-async-generator-fixture/92). Could your PR also resolve this case as well?

This is still happening with Sphinx 4.3 and sphinx-autodoc-typehints 1.12.0, on Python 3.10. @cblegare's PR is about fixing the issue only for `async def` lines, but my issue is unrelated...

We could use two-phase cancellation: requesting cancellation after 1st timeout, cancel cancellation after 2nd timeout if it takes too long, with help of `Task.uncancel()` and cancellation scopes to be introduced...

Let's postpone adoption of tokio as it currently requries the nightly version of Rust and its installation process needs some touches.

I'd like to see this applied to the release, though it seems to be updated to work with the latest master.

This issue is analogous to #45 .

Maybe related to my PR #42. I think `compiled._bind_processors` should do the necessary work here. @alejandrorosas Could you please show the table schema (in SQLAlchemy Table definitions) and the Python...

Could you show us the details of your configurations, such as PHP memory limit, timeout (execution time limit), and maximum output bytes allowed (in either webserver or PHP)? And if...

gzip 인코딩과 PHP의 flush를 같이 사용하는 경우 이슈가 좀 있는 것 같습니다. 아직 저도 직접 실험해보지는 못했어요; (텍큐 코드에 flush를 쓰는 부분이 있는지는 저도 확인을 해봐야...) http://stackoverflow.com/questions/12165810/how-to-disable-output-buffering-in-nginx-for-php-application http://stackoverflow.com/questions/4870697/php-flush-that-works-even-in-nginx

이미 알고 있는 문제입니다만, 고치려면 플러그인의 자바스크립트 지원에 대한 전체적인 리팩토링이 필요해서 나중 구현으로 미뤄둔 상태입니다. #1732 이슈와 함께 처리할 예정입니다.