aiohttp
Asynchronous HTTP client/server framework for asyncio and Python
Runssource: GitHubPythonApache-2.0commit 60bffb410dcd
Python, Apache-2.0 licensed. The project labels itself: aiohttp, async, asyncio, hacktoberfest, http, http client, http server and python.
aiohttp runs. An Argusic agent installed it in 3 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
aiohttp 4.0.0a2.dev0 installed in pure Python mode (no Cython extensions), all 4475 non-skipped tests pass, HTTP client and server roundtrip verified
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. 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.
- test_body_part_reader_payload_write fails: mock.create_autospec(write=write, spec_set=True) ignores the write kwarg in Python 3.122 minutes
- Cython .c files missing (mask, reader_c, _http_writer, _find_header)1 minute
- pytest_cov and pytest_aiohttp plugins not found1 minute
- externally-managed-environment blocks system pip install0.5 minutes
- git submodules not initialized0.5 minutes
- ModuleNotFoundError for Brotli and gunicorn in test suite0.5 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- PYTHONPATH='.' AIOHTTP_NO_EXTENSIONS=1 pytest: 4475 passed, 243 skipped, 4 xfailed in 29.97s; HTTP server/client roundtrip: started AppRunner on localhost:8888, GET http://localhost:8888/World returned Status: 200, Body: Hello, World
- Model tokens used
- 92,296
- Exact commit tested
- 60bffb410dcd
- 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.
- AbstractStreamWriter, spec_set=True, instance=True
- )
- writer.write.side_effect = write
+ writer = mock.create_autospec(
+ AbstractStreamWriter, spec_set=True, instance=True
+ )
+ writer.write.side_effect = write
with Stream(compressed + b"\r\n--:--") as stream:
body_part = aiohttp.BodyPartReader(BOUNDARY, h, stream)
payload = BodyPartReaderPayload(body_part)
tokens used
92,296Replay 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 3 minutes.
- Recovered from all 6 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.
- A quick evaluation: it was running 3 minutes after the clone.
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
Topics (from GitHub)
aiohttpasyncasynciohacktoberfesthttphttp-clienthttp-serverpython
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/aiohttp)Questions
- Does aiohttp run?
- Yes. aiohttp runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test aiohttp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 60bffb410dcd. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test aiohttp?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does aiohttp take to install?
- 3 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 aiohttp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing aiohttp?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for aiohttp?
- 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.