metatube-sdk-go

MetaTube SDK & API Server in Golang

Could not verifysource: GitHubhomepageGoApache-2.0commit 19a92ad3263a

Go, Apache-2.0 licensed. The project labels itself: cloudnative, emby, gin, go colly, gorm, jellyfin, pigo face detection and postgresql.

Argusic could not get metatube-sdk-go running. An Argusic agent installed it in 3 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

MetaTube SDK Go server builds and runs on this system, serving its REST API on port 8080 with SQLite storage. Provider and translate tests fail due to unreachable external websites and missing third-party API keys, no code-level defects were found.

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

At a glance

verdict
Could not verify
Argusic Score
50 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
878
forks
216
open issues
8
watchers
7
size
10 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 metatube-sdk-go, 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.

  • Go 1.26 not installed in container1 minute
  • Provider tests fail due to external sites being unreachable (aventertainments, duga, faleno, fanza, fc2, fc2hub, fc2ppvdb, gcolle, getchu, gfriends, jav321, javbus, javfree, kin8tengoku, mgstage, pcolle, sod, tokyo-hot)
  • Translate tests fail (baidu 52003 unauthorized, deepl 403, google needs API key, googlefree 400, openai 401)
  • engine/dbengine test fails: Docker socket not available
Install time
3 minutes
Cold machine to finish
18 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
make development compiled 47MB binary; ./build/metatube-server -dsn 'file:test.db?cache=shared' started, auto-created SQLite tables, responded to GET / with HTTP 200 and JSON body. go test ./... ran, 30+ packages passed (collections, common utils, detector, imageutil, envconfig, provider/imcmp, madouqu, theporndb, etc.)
Model tokens used
291,150
Exact commit tested
19a92ad3263a
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
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

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

  _ "github.com/lib/pq"
  "github.com/ory/dockertest"
  "github.com/ory/dockertest/docker"
  "github.com/stretchr/testify/assert"
  "github.com/stretchr/testify/require"
  "github.com/stretchr/testify/suite"
Now I have the complete picture. Here's the assessment:
2026-10-12T19:33:44.120589Z ERROR codex_core::session: failed to record rollout items: thread 01a13…
2026-10-12T19:33:44.120644Z ERROR codex_core::session: failed to record rollout items: thread 01a13…
tokens used
291,150
Now I have the complete picture. Here's the assessment:

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 3 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • 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

  • An agent with no time limit did not get it running.

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/3Did not run20.000.06
Argusic Runner1/3Unverified80.000.07

Topics (from GitHub)

cloudnativeembygingo-collygormjellyfinpigo-face-detectionpostgresqlscraper-enginesqlite

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/metatube-sdk-go.svg)](https://argusic.com/subject/metatube-sdk-go)

Questions

Does metatube-sdk-go run?
Argusic could not verify that metatube-sdk-go runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test metatube-sdk-go?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 19a92ad3263a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test metatube-sdk-go?
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 metatube-sdk-go 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 metatube-sdk-go need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing metatube-sdk-go?
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 metatube-sdk-go?
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