Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    My guess is that you are likely hitting some kind of "deadlock" - for example, one asycnio task could be awaiting for something which indirectly is awaiting itself. My suggestion is to try to pick your full code, and strip it out in batches, mocking I/O calls for asyncio.sleep, and try to get a minimal amount of Python code wich maintains the current behavior. (them either update the question, or more likely, you will have your answer already) Commented Jul 8, 2024 at 16:21
  • 2
    @jsbueno it only happens on our test servers and only after 10-20 minutes, and redeploy takes another 30 min so it's really hard to do such things. Also the code is way too large to do such ablation study. What I realize is that if I use the pure python version of the asynciomodule instead of the C one (I just delete the asynciomodule.so library), then it seems to run without hiccup. It was also running fine before we migrate to Python 3.12. So it's likely some kind of bug in CPython Commented Jul 8, 2024 at 19:00
  • 2
    "So it's likely some kind of bug in CPython" - well, I have to agree with that. Unfortunatelly, it will be hard to pinpoint. Commented Jul 8, 2024 at 19:24
  • @jsbueno Downgrading to Python 3.11.9 fixed the issue for us. Commented Jul 15, 2024 at 11:24
  • 1
    yes. the problem is that this issue will keep loomkng there. Did you fill in a bug reoprt fro cpython? If not, please do so. Commented Jul 15, 2024 at 12:04