P3-01: workers config parsed but unused by ThreadingHTTPServer #19

New issue

Closed

opened 2026-06-16 13:57:02 +00:00 by Artur · 0 comments

Artur commented

2026-06-16 13:57:02 +00:00

Owner

Severity: P3 (Low)
File: decider/server.py lines 95, 210

Problem

workers = _server_config.get("workers", 4)  # parsed but never used
...
server = ThreadingHTTPServer((bind, port), DeciderHandler)  # unbounded thread pool

The workers config is read from the config file, logged, but never applied. ThreadingHTTPServer spawns a new thread per request with no cap.

Fix

Either:

Remove workers from config (document that ThreadingHTTPServer is unbounded)
Or implement a bounded thread pool executor that queues requests

**Severity**: P3 (Low) **File**: `decider/server.py` lines 95, 210 ## Problem ```python workers = _server_config.get("workers", 4) # parsed but never used ... server = ThreadingHTTPServer((bind, port), DeciderHandler) # unbounded thread pool ``` The `workers` config is read from the config file, logged, but never applied. `ThreadingHTTPServer` spawns a new thread per request with no cap. ## Fix Either: 1. Remove `workers` from config (document that ThreadingHTTPServer is unbounded) 2. Or implement a bounded thread pool executor that queues requests

Artur added the

enhancement

P3-Low

labels

2026-06-16 13:57:02 +00:00

Artur referenced this issue from a commit

2026-06-16 13:59:15 +00:00

fix: P2-01, P2-04, P3-01, P3-02, P3-03, P3-04, P3-05

Artur closed this issue

2026-06-16 14:24:07 +00:00