eho/register-referentie
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

fix: cap Objecten/Objecttypen uWSGI to 1 worker — unstarve verify-stack e2e (closes #144) #145

Merged
not merged 1 commits from fix/144-verify-stack-uwsgi into main 2026-07-27 13:07:56 +00:00
Conversation 0 Commits 1 Files Changed 2
+14
1 Commits
Author SHA1 Message Date
notandClaude Opus 4.8 802f0e2c65 fix(infra): cap Objecten/Objecttypen uWSGI to 1 worker — unstarve verify-stack e2e (closes #144)
CI / build (pull_request) Successful in 1m26s
Details
CI / lint (pull_request) Successful in 1m38s
Details
CI / unit (pull_request) Successful in 2m18s
Details
CI / frontend (pull_request) Successful in 4m50s
Details
CI / mutation (pull_request) Successful in 7m14s
Details
CI / verify-stack (pull_request) Successful in 10m49s
Details 
The Maykin images run uWSGI with 4 processes × 4 threads by default. Two
web services × 4 idle Django workers (~200 MB each) sat idle during the
Playwright e2e step and starved the single shared CI runner, so Keycloak
and the portals stopped responding (login never loaded) and Chromium
crashed — main verify-stack went red from run 2177 (post-#142) onward
while the PR runs passed on a less loaded runner.

These APIs only serve single-request smoke checks and are idle during
e2e, so 1 worker is plenty. Verified locally: both services healthy with
UWSGI_PROCESSES=1 and make verify-objecten / verify-objecttypen still green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-07-27 13:38:47 +02:00