riko

A Python stream processing engine modeled after Yahoo! Pipes

Runssource: GitHubPythonMITcommit dcfa9f2bd4ba

Python, MIT licensed. The project labels itself: asynchronous, cli, data, etl, featured, functional programming, library and parallelism.

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

All 1090 non-slow tests pass, riko 0.77.3 imports and runs, CLI manage/run-pipe/benchmark commands work, SyncPipe/AsyncPipe stream pipelines produce correct output.

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.58 (measured)
recorded runs
2
last tested
stars
1,605
forks
75
open issues
16
watchers
46
size
15 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 riko, 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.

  • PYTHONHASHSEED not set for deterministic hash() values - tests using hash() produced inconsistent results8 minutes
  • Golden codegen files (pypipelines/*.py, _configs.py, _module_ids.py) stale relative to current Jinja2 template output6 minutes
  • CLI scripts (run-pipe, benchmark) not found by subprocess tests - venv bin/ not on system PATH5 minutes
  • manage test command failed to find pytest (shutil.which("pytest") returns None in venv)3 minutes
  • test_codegen_renders_top_level_count assertion expects count=\"first\" (double quotes) but Python 3.12 repr() uses single quotes2 minutes
  • Missing tzdata package for timezone resolution (ZoneInfo requires tzdata on Linux)1 minute
Install time
26 minutes
Cold machine to finish
68 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
pytest --tb=line -q --no-cov -m not slow with PYTHONHASHSEED=94967295 PATH=.venv/bin:$PATH: 1090 passed, 4 xfailed, 0 failed
Model tokens used
396,148
Exact commit tested
dcfa9f2bd4ba
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.

Let me verify `manage test` works standalone (the fix should handle PYTHONHASHSEED internally):
exec
/bin/sh -lc 'cd /work/repo && timeout 30 .venv/bin/manage test --no-cov -w "tests/public/test_colle…
 succeeded in 2875ms:
=========================== short test summary info ============================
XFAIL tests/public/test_collections.py::TestSyncCollections::test_lifecycle_markers_do_not_leak_int…
XFAIL tests/public/test_collections.py::TestSyncCollections::test_idle_drain_ends_the_pass_not_the_…
======================== 53 passed, 2 xfailed in 0.42s =========================
The `manage test` command now works standalone (without needing PYTHONHASHSEED manually set). Final…
tokens used
396,148
The `manage test` command now works standalone (without needing PYTHONHASHSEED manually set). Final…

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 25.5 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 MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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.58
Argusic Runner1/3Runs100.000.17

Topics (from GitHub)

asynchronousclidataetlfeaturedfunctional-programminglibraryparallelismrssstream-processing

Embed the badge

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

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

Questions

Does riko run?
Yes. riko runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test riko?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit dcfa9f2bd4ba. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test riko?
The run that produced this verdict cost $0.58: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does riko take to install?
25.5 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 riko need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing riko?
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 riko?
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