pingap
A reverse proxy like nginx, built on pingora, simple and efficient.
Runssource: GitHubhomepageRustApache-2.0commit 71c4aa98aade
Rust, Apache-2.0 licensed. The project labels itself: pingora and reverse proxy.
pingap runs. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Pingap 0.14.3 reverse proxy binary builds, test suite passes (413/413), binary serves HTTP requests on a configured port, responds to /ping with 200 'pong', and handles graceful shutdown.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing protoc (protobuf compiler) for etcd-client build dependency3 minutes
- Expired test certificate caused test_cert assertion failure (not_after 2026-10-06 < current date 2026-10-08)3 minutes
- No admin web assets in dist/ caused AdminAsset::get('index.html') to return None, failing test_embedded_static_file2 minutes
- test_etcd_config_manger requires running etcd at 127.0.0.1:2379, which is not available1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --workspace exited 0 (413 passed, 1 ignored); curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:9092/ping returned 200 with body 'pong'
- Model tokens used
- 85,227
- Exact commit tested
- 71c4aa98aade
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All tests pass (351 total, 0 failures). The only ignored test is `test_etcd_config_manger` which re…
Let me gather all the key facts for the final report.
exec
/bin/sh -lc 'cd /work/repo && export PATH="/tmp/protoc/bin:$HOME/.cargo/bin:$PATH" && cargo test --…
succeeded in 8255ms:
Total: 413 passed, 0 failed, 1 ignored
All verified. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 15, "e…
tokens used
85,227
All verified. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 15, "e…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 15 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pingap)Questions
- Does pingap run?
- Yes. pingap runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test pingap?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 71c4aa98aade. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test pingap?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pingap take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does pingap need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pingap?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for pingap?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.