EPlusTV

Virtual linear channels for various providers

Runssource: GitHubTypeScriptMITcommit 10dd938b8ec1

TypeScript, MIT licensed. The project labels itself: channels dvr server, custom channels, jellyfin, livetv, tvheadend and xmltv.

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

The EPlusTV Hono server starts on port 8000, serves the config web UI, generates 200 virtual channels in both M3U and XMLTV formats, and all 22 provider handlers initialize successfully as disabled stubs awaiting credentials.

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.06 (measured)
recorded runs
1
last tested
stars
297
forks
52
open issues
36
watchers
17
size
11 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 EPlusTV, 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.

  • npm ci exit 2: 'Bad substitution' from husky prepare script in sh0.5 minutes
  • yt-dlp binary missing (not on PATH)
  • TypeScript 4.4.3 cannot parse [email protected] / [email protected] types (TS1005 on ???)
Install time
8 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
curl -s -w '%{http_code}' http://127.0.0.1:8000/ returned 200; curl http://127.0.0.1:8000/channels.m3u returned 200 with 600 lines (200 channel URLs); curl http://127.0.0.1:8000/xmltv.xml returned 200 and validated via XML parser (200 channels, valid structure).
Model tokens used
100,277
Exact commit tested
10dd938b8ec1
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.

now = time.time()
with open('/tmp/start_time','r') as f:
    start = int(f.read().strip())
secs = int(now) - start
print(f'Total mission: {secs}s = {secs/60:.1f} minutes')
\"" in /work/repo
 succeeded in 0ms:
Total mission: 497s = 8.3 minutes
All verified. Here's my final report.
tokens used
100,277
All verified. Here's my final report.

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 8.3 minutes.
  • Recovered from all 3 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.
  • A quick evaluation: it was running 8.3 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

channels-dvr-servercustom-channelsjellyfinlivetvtvheadendxmltv

Embed the badge

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

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

Questions

Does EPlusTV run?
Yes. EPlusTV runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test EPlusTV?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 10dd938b8ec1. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test EPlusTV?
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 EPlusTV take to install?
8.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 EPlusTV need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing EPlusTV?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for EPlusTV?
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