Repository navigation
fix(requirements): bump uWSGI 2.0.28 -> 2.0.31 (restore CodeQL 'Analyze (python)' green) - #4146
RanaKhan77 wants to merge 4 commits into
Conversation
uWSGI 2.0.28 no longer builds a wheel in the CodeQL 'Analyze (python)' job (Install dependencies step) since ~Nov 10 - the ubuntu-latest toolchain moved to GCC 15, which 2.0.28 predates. 2.0.31 carries the modern-compiler build fixes. Details and evidence: intelowlproject#4145 (comment)
|
Follow-up on the
If it helps, I can try to pin down the exact transitive culprit by diffing a Net effect of this PR on checks: |
The backend-tests failure on the previous run was transient (the same job failed intermittently on other branches in the same window and is green again on newer runs) - see the analysis comment on the PR.
|
CI status analysis (backend-tests failure on the initial run): The failure was unrelated to this one-line requirements bump - it happens during container startup, before any test runs: The same job failed intermittently on other branches in the same window with no related changes:
This points to a transient runner/base-image issue (the same environment shift that breaks the uWSGI 2.0.28 wheel build in the CodeQL job - see the analysis on #4145). I pushed an empty commit to re-trigger the checks. |
…ect#4036 for master) Same fix the maintainers merged on develop in intelowlproject#4036: without the pin, the image build's certego-saas install resolves django-ipware 8.x, which forces Django 5.2 and crashes startup in api_app/choices.py (TextChoices rejects PosixPath - issue intelowlproject#4034). Master still lacks the pin, so fresh master builds fail backend-tests deterministically.
|
backend-tests root cause found (correction to my earlier "transient" read - it is deterministic on fresh builds): The This is issue #4034: the image build's second I pushed the same pin here (one requirements line, mirroring the merged develop fix) so this PR's checks can run on the intended dependency set. The CodeQL |
Third fresh-resolve break: with django-ipware pinned the container starts and tests run, but kombu 5.6.x (freshly resolved under celery 5.4.0's <6.0 bound) raises VersionMismatch: Redis transport requires redis-py>=6.1.0 while the image resolves redis-py 5.3.1. Pinning kombu to the celery 5.4.0 companion version keeps the resolved set consistent. Same pins exist on develop, so fresh develop builds are affected too (warm docker-layer caches mask it).
|
Update — third and final fresh-resolve root cause: with
I pinned
|
|
Small correction to my last comment so nobody chases a ghost: after the final push ( Current checks on the branch: Build & Tests ✅ CodeQL ✅ linters ✅ dependency-review ✅ (runs 43521057229 / 43521057205 / 43521057206). So the one-line bump is CI-clean and ready for review whenever someone has a moment. |
What
Bumps the
uWSGIpin inrequirements/project-requirements.txtfrom2.0.28to2.0.31(one line).Why
The Analyze (python) CodeQL job has been failing repo-wide since ~Nov 10 at the
Install dependenciesstep:pip install -r requirements/project-requirements.txtfails withFailed to build uWSGI/failed-wheel-build-for-install.Evidence that this is environmental (not PR-specific):
feat/trufflehog-analyzerpassed CodeQL on Nov 7 (run 42355896990) and fails on Nov 12 (run 43200723154) with no workflow change in between.ubuntu-latestrolling to a newer image with GCC 15 is the likely trigger. uWSGI 2.0.28 predates the stricter toolchains; releases after it (2.0.29+) contain build fixes for newer compilers.Verified locally: 2.0.28 still builds on Debian GCC 14 / Python 3.11 (so the failing combination is specifically the newer runner toolchain); 2.0.31 is the current release with the modern-compiler fixes.
Related existing discussions about uWSGI's future: #3375, #3387. This bump is intentionally minimal — it should restore the green checks without touching the planned Gunicorn migration.