mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Opus 5
9956498a95
An APIRequestContext inherits use.proxy from playwright.config.js:71, so on an onion pass the addon spec posted to the translation gateway through Tor and got HostUnreachable. That is not a routing fault: web-svc-translate variant 1 pins tor.enabled false, because an engine consumed over the internal network publishes no onion surface, so there was nothing for Tor to reach.
The gateway call now runs on its own request context that keeps the proxy and bypasses only that one host, and only when the host is not itself an onion, so a round where web-svc-translate does publish an onion surface still goes through Tor. The context is disposed in a finally. Both assertions are unchanged: no retry, no raised timeout, no skip.
Superseded once feature/network/multi-network-serving lands. 857639db2b solves this class at harness level through plugins/lookup/browser_proxy_bypass.py and PLAYWRIGHT_PROXY_BYPASS, deriving the bypass list from the deployed applications domains plus the issuer, and it removes exactly this pattern from test-mailflow.js and test-onion-mailflow.js because a spec that passes its own proxy to newContext drops the harness bypass. That branch is 106 commits ahead and 1493 behind, so cherry-picking it would drag a cross-cutting networking change into an i18n branch. When it merges, this spec goes back to the plain request fixture.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>