Uvicorn segfaults in a certain GitHub Action #2557
Unanswered
vytas7
asked this question in
Potential Issue
Replies: 1 comment
-
I've never seen this before, and I just found out that there was a bind in This doesn't look related to the other issues. It doesn't look like a Uvicorn issue, since it mentions all the cython related packages. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Recently we have a encountered a strange issue when running Falcon's E2E tests against Firefox. These tests spawn a Falcon (ASGI flavour) app, and interact with its WebSocket/SSE functionality from the browser.
I thought that it was a new version of Firefox, Selenium driver, or similar, and simply disabled the test, given it is not our top focus, and the Chrome E2E test is still working fine.
However, a member of our community @Cycloctane has now traced the problem to be caused by a segfault in Uvicorn, not sure what to make of it:
Can it be a genuine issue in one of Uvicorn's extension modules?
Or is it anything odd in that GitHub Actions environment, and not a real issue?
Or could it be a real issue but only when handling an edge case such as OoM, running out of file handles, etc.
It seems we cannot really reproduce the issue outside of the said GitHub Actions environment. The same test works fine against Chrome.
However, the Firefox CI gate seems to be failing in a 100% reproducible fashion. As I understand from Cycloctane's experiments, using Python 3.11 works, but trying to use other CPython 3.12 minor versions, or a different Ubuntu version, etc, makes no difference.
I skimmed through recent Uvicorn issues, and many seem to be complaining about workers getting killed (see, e.g., #2450, #2506, etc), but at first glance it doesn't really seem to be the same segfault.
Beta Was this translation helpful? Give feedback.
All reactions