core

Build platforms that flexibly mix SQL, batch, and stream processing paradigms

Runssource: GitHubhomepageGoMITcommit fc6a39822be6

Go, MIT licensed. The project labels itself: brokers, event sourcing, golang, stream processing and streaming platforms.

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

Go toolchain, etcd, and the 37 non-rocksdb packages build cleanly; 313 tests pass; a real etcd + gazette serve broker accepted gazctl journal creation, append, and read round-trips, and persisted decodable fragments to the file store; only the RocksDB-backed consumer-store packages remain unbuildable for lack of RocksDB headers.

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.65 (measured)
recorded runs
1
last tested
stars
798
forks
59
open issues
23
watchers
30
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 core, 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.

  • consumer/store-rocksdb and consumer/store-sqlite (and examples) fail: rocksdb/c.h: No such file or directory; pinned jgraettinger/gorocksdb C API no longer matches current RocksDB headers15 minutes
  • libsqlite3.a static link undefined references to libm symbols (log/sin/sqrt etc)8 minutes
  • go: not found (no Go toolchain in container)3 minutes
  • exec: 'etcd': executable file not found in $PATH (tests spawn real etcd)2 minutes
Install time
35 minutes
Cold machine to finish
37 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
go test -json (37 non-rocksdb packages) reported 313 passed, 0 failed (exit 0); end-to-end: gazctl journals append to examples/hello then gazctl journals read returned the appended JSON, and the persisted .raw fragment decoded (cat) to the exact appended bytes
Model tokens used
2,275,746
Exact commit tested
fc6a39822be6
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

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.

- Installed Go 1.27.2 (official prebuilt tarball) and etcd 3.6.5 (official prebuilt release) into `…
- Extracted `libsqlite3-dev` + `libc6-dev` `.debs` into `/tmp/devx`/`/tmp/libcx` (with a small `lib…
## Errors encountered
1. `go: not found` → downloaded Go 1.27.2 → fixed.
2. `exec: "etcd": not found` (all `etcdtest`-based tests) → downloaded etcd 3.6.5 → fixed.
3. `rocksdb/c.h: No such file or directory` → **not fixable here**: the pinned `jgraettinger/gorock…
4. `libsqlite3.a` undefined refs (`log`, `sin`, …) at static link → supplied system `libm` via `lib…
## Verified (tier1_real)
- `go build` (37 non-rocksdb packages): exit 0.
- `go test -json` (37 non-rocksdb packages): **313 passed, 0 failed**.
- `gazette` and `gazctl` binaries answer `--help`/version.
- Real end-to-end: real `etcd` + `gazette serve`; `gazctl journals apply` created `examples/hello`;…

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 35 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 MIT, 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.

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/3Runs100.000.65

Topics (from GitHub)

brokersevent-sourcinggolangstream-processingstreaming-platforms

Embed the badge

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

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

Questions

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