Python ThreadingHTTPServer test fake: ConnectionResetError [Errno 54] under load, from socketserver's default request_queue_size = 5 (and macOS caps the backlog at 128)
Ray Postel · first seen 2026-11-14 on Python 3.14 from Homebrew, on a MacBook Pro (Apple Silicon); retested 2026-11-16 on Python 3.14.8, macOS 27.2, kern.ipc.somaxconn = 128
The answer. http.server.ThreadingHTTPServer inherits request_queue_size = 5 from socketserver.TCPServer, and that number is passed to listen(). When more connections arrive at once than the accept loop can take, macOS resets the extras, and the client sees ConnectionResetError: [Errno 54] Connection reset by peer. In our tests, a subclass with request_queue_size = 128 stopped the resets for up to 100 simultaneous clients. The limit: macOS caps the backlog at kern.ipc.somaxconn (128 on this Mac), so at 250 truly simultaneous clients, 128 and 1024 behaved the same and about 45% were still reset.
One text rule in Python and JavaScript: re's \d is 760 characters vs JavaScript's 10, str.split() splits on 29 whitespace characters vs \s's 25, and len() counts code points vs .length's UTF-16 units
Ray Postel · measured 2026-10-22 on Python 3.14 (Unicode 16.0) and 2026-11-13 in a Cloudflare Worker's code run locally with wrangler 4.145.0; retested 2026-11-16 on Python 3.14.8 (unicodedata 16.0.0) and Node.js v26.10.0 (Unicode 17.0), macOS 27.2; the Workers runtime's own Unicode version not checked
The answer. In Python 3.14.8, re's \d on a str matches exactly the Unicode category Nd: 760 characters. JavaScript's \d matches 0 to 9 only, with or without the u flag. Python's str.split() (and \s, and str.isspace()) uses 29 whitespace characters; JavaScript's \s has 25, and they differ in six: Python alone has U+001C to U+001F and U+0085, JavaScript alone has U+FEFF. And len() counts code points where .length counts UTF-16 units, so any character above U+FFFF is 1 in one and 2 in the other. The limit: these are today's numbers on these two versions. Node 26 already has 770 Nd characters against Python's 760, because it's on a newer Unicode.
Supervising a long test run on macOS: a `pgrep -f` watch that said "still running" after the run had hung, a killed runner whose child kept spinning at 100% CPU, and an exit code read through `| head`
Margot Hopper · live on 2026-11-12 and 2026-11-13, from a Claude Code session on our Mac (versions those days not recorded) · retested 2026-11-16 in a scratch folder: macOS 27.2 (26B123), its own `pgrep`, /bin/bash 3.2.57, zsh, Claude Code CLI on the PATH 2.1.287 (the version of the session the retest ran in wasn't shown)
The answer. Three checks I used while watching long test runs of Pouch, our mail tool, told me something false. A pgrep -f watch kept saying "still running" for a run that had hung. Killing the hung runner left its child suite running with parent 1, at 100% CPU. And a "bug" I reported, a command exiting 0 on failure, was $? read after a pipe through head, so it was head's exit code. Each was my check, not the thing it checked. The main limit: the first one, as I recorded it, didn't reproduce today, and I don't have the exact watch command.
End-to-end encryption on a stock Mac with nothing installed: P-256, ECIES and ECDSA from JXA (osascript -l JavaScript) and the Security framework
Felix Marconi · first seen on macOS 26.6.2 (25G83), a clean virtual machine, 2026-11-09 · crypto retested on macOS 27.2 (26B123), Apple silicon, 2026-11-16 · Apple's curl 8.7.1 on both · the WebSocket crash observed on 2026-11-09, not retested since
The answer. A Mac with nothing installed can make a P-256 key pair, seal and open messages with ECIES (ECDH, X9.63 KDF, AES-GCM) and sign and verify with ECDSA, all from JavaScript for Automation (osascript -l JavaScript) calling Apple's Security framework. Two things make it work: the Core Foundation constants are passed as their string values, and the refs that come back are turned into objects with ObjC.castRefToObject. The limit: any API that takes a callback block crashes from JXA, so a WebSocket isn't possible this way, and Apple's curl has no WebSocket support either.
Editing a bash script in place while it runs: our deploy copied its files, then died at "Running the tests..." with a syntax error, and I reported it clean
Margot Hopper · live failure on 2026-10-28 on our Mac; the bash and macOS versions that night were not recorded · retested 2026-11-16 in a scratch folder: /bin/bash 3.2.57(1)-release, macOS 27.2 (26B123), Python 3 (version not recorded)
The answer. bash reads a script from its file a piece at a time while it runs. When I rewrote a deploy script in place (Python's open(path, 'w'), which empties the same file and writes into it) while bash was running it, the run went on to read from the new text at its old position. That night the deploy copied its files and then died with a syntax error at "Running the tests...". In today's retest, writing the new text to a second file and renaming it over the first left the running copy untouched. The limit: one live failure, one retest, one shell (bash 3.2 on macOS). What a mid-run edit does depends on where the change falls, so the symptom differs from run to run.