restc-cpp

Modern C++ REST Client library

Runs with mockssource: GitHubC++MITcommit a8cd803d097f

C++, MIT licensed. The project labels itself: asio, c plus plus, coroutines, http client, json, json serialization, rest and rest client.

restc-cpp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Library builds with Boost 1.83, OpenSSL 3.0, and zlib 1.3. Static archive librestc-cpp.a produced. All 6 unit tests pass. basic_tests functional test suite passes against a mock HTTP/1.1 server.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
1
last tested
stars
651
forks
96
open issues
55
watchers
44
size
1 MB
created
last push

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.

Time lost to each failure while testing restc-cpp, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Boost libraries not installed on system (no root)8 minutes
  • Functional tests require Docker containers (nginx, json-server, squid, socks) not available in this environment4 minutes
  • zlib1g-dev not installed (no root)3 minutes
Install time
15 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
ctest in /tmp/build4: 6/6 unit tests passed (URL, JSON, JSON_IOSTREAM, HTTP_REPLY, ASYNC_SLEEP, REQUEST_BUILDER). basic_tests: 5/5 passed with Python HTTP/1.1 mock server on port 3001. HTTPS test reached real server lastviking.eu successfully.
Model tokens used
175,060
Exact commit tested
a8cd803d097f
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
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

5/6 Test #5: ASYNC_SLEEP_TESTS ................   Passed    1.21 sec
    Start 6: REQUEST_BUILDER_TESTS
6/6 Test #6: REQUEST_BUILDER_TESTS ............   Passed    0.00 sec
100% tests passed, 0 tests failed out of 6
Total Test time (real) =   1.22 sec
exec
/bin/sh -lc 'pkill -f "mock3.py" 2>/dev/null; true' in /work/repo
 exited 143 in 0ms:
Here is the final result:
tokens used
175,060
Here is the final result:

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

  • Installed in 15 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.07

Topics (from GitHub)

asioc-plus-pluscoroutineshttp-clientjsonjson-serializationrestrest-client

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/restc-cpp.svg)](https://argusic.com/subject/restc-cpp)

Questions

Does restc-cpp run?
restc-cpp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test restc-cpp?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a8cd803d097f. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test restc-cpp?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does restc-cpp 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 restc-cpp need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing restc-cpp?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for restc-cpp?
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.

Discussion