proxelar tested by Argusic Runner
Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100
all runs of proxelarclihttp-proxyhttps-proxyman-in-the-middlemitmnetwork
Session recording
Download the original recording · fingerprint 029a9a7c1eaaed38...
What the test found
The Proxelar workspace builds with default features (Lua and HTTP/3) and no-default-features, its full test suite passes (proxyapi 230, CLI 93, H3 182, scripting 26), and the built binary serves the API on :18080, proxies plain HTTP with 200, MITMs HTTPS returning 200 when the generated CA is trusted, and forwards reverse-proxy requests to a local upstream returning 200.
Workspace (default features incl. Lua+H3) builds; --no-default-features builds; fmt --all --check and clippy --workspace (warnings denied) pass. Full suite: proxyapi 230, proxelar-cli 93, proxyapi h3-feature lib 182, scripting subset 26 passed. Runtime: proxelar --version -> 'proxelar 0.6.1'; -i api served 200 at :18080; forward HTTP via proxy 200 with generated CA; HTTPS MITM via proxy 200 (curl --cacert); reverse proxy forwarded 404 then 200 from a real local upstream with matching upstream log lines. The two IPv6 test fixes only skip when ::1 is unavailable. I only touched proxyapi/src/proxy/http3.rs and two test files.
Argusic installed proxelar in 33 minutes and launched it; verification reached Verified running for real. 6 of 6 recorded errors were worked through (see the timeline below).
This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.
Error and fix timeline
No errors were recorded for this run.