ruia

Async Python 3.6+ web scraping micro-framework based on asyncio

Runssource: GitHubhomepagePythonApache-2.0commit 68a45028830a

Python, Apache-2.0 licensed. The project labels itself: aiohttp, asyncio, asyncio spider, crawler, crawling framework, middlewares, python and python ruia.

ruia runs. An Argusic agent installed it in 8 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Ruia 0.8.5 installed and fully functional inside a venv at /tmp/ruia-venv; all 67 tests pass, package importable as ruia.__version__ == '0.8.5'.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.13 (measured)
recorded runs
2
last tested
stars
1,739
forks
187
open issues
9
watchers
38
size
5 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 ruia, 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.

  • Module-level async code in test_response.py raised RuntimeError: no current event loop (Python 3.12 + uvloop)3 minutes
  • Spider.__init__ eagerly creates ClientSession() requiring a running event loop (aiohttp 3.14+ change)2 minutes
  • start_worker crashed on 2-tuple results from handle_callback: AttributeError on close_request1 minute
  • test_request_url scrapes live Hacker News - HTML changed, NothingMatchedError1 minute
Install time
8 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
cd /work/repo && /tmp/ruia-venv/bin/python -m pytest tests/ -q exited 0, 67 passed in 11.38s
Model tokens used
290,934
Exact commit tested
68a45028830a
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.

- `ruia/spider.py` — made `ClientSession` creation lazy (`None` instead of eager) for aiohttp 3.14+…
- `tests/test_item.py` — replaced live Hacker News scrape with a local HTML fixture
- `tests/data/for_hn_testing.html` — new test fixture for Hacker News item parsing
2026-11-13T16:29:16.378370Z ERROR codex_core::session: failed to record rollout items: thread 01a1d…
tokens used
290,934
The full test suite passes — here's the summary:
**Changes made (4 files):**
- `tests/conftest.py` — new file: sets an event loop before module-level test code runs, fixing `Ru…
- `ruia/spider.py` — made `ClientSession` creation lazy (`None` instead of eager) for aiohttp 3.14+…
- `tests/test_item.py` — replaced live Hacker News scrape with a local HTML fixture
- `tests/data/for_hn_testing.html` — new test fixture for Hacker News item parsing

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.
  • 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 8 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.

Of the 5 aiohttp projects Argusic has installed and timed, ruia was the 5th fastest to reach a running state, and 4 of 5 reached one at all.

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 8 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.13
Argusic Runner1/3Runs100.000.08

Topics (from GitHub)

aiohttpasyncioasyncio-spidercrawlercrawling-frameworkmiddlewarespythonpython-ruiaruiaspideruvloop

Embed the badge

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

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

Questions

Does ruia run?
Yes. ruia runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test ruia?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 68a45028830a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ruia?
The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ruia take to install?
8 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 ruia need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ruia?
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.
How does ruia compare with the alternatives?
Of the 5 aiohttp projects Argusic has installed and timed, ruia was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for ruia?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion