bili-sync
由 Rust & Tokio 驱动的哔哩哔哩同步工具
Runssource: GitHubhomepageRustMITcommit cc9a77aa4934
Rust, MIT licensed. The project labels itself: bilibili, bilibili api, bilibili download, emby, jellyfin and nas.
bili-sync runs. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
bili-sync compiles, all 33 unit tests pass, the binary launches and serves the web UI on port 12345, the frontend builds cleanly
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Rust toolchain not installed1 minute
- Node.js v18 was too old for frontend build dependencies (required ^20.19.0)1 minute
- npm install failed due to engine conflict with @eslint/compat
- Install time
- 6 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test exited 0, 33 passed 0 failed; binary --help printed expected usage; binary startup logged DB init, config init, and web server startup then cleanly shut down on timeout
- Model tokens used
- 39,335
- Exact commit tested
- cc9a77aa4934
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
5. **Binary** — `./target/debug/bili-sync-rs --help` prints usage; starting it initializes DB, laun… 6. **Tests** — `cargo test` reports 33 passed, 0 failed, 7 ignored tokens used 39,335 The app is fully working. Let me compile the final report. **Summary of work:** 1. **Rust toolchain** — installed via rustup (1.98.0, matching the project's `rust-toolchain.toml`) 2. **Node.js** — upgraded from v18 to v22.23.2 via nvm (the frontend build required Node ≥20) 3. **Frontend** — `npm install` && `vite build` succeeds, output written to `web/build/` 4. **Backend** — `cargo build` compiles all 3 crates with no errors 5. **Binary** — `./target/debug/bili-sync-rs --help` prints usage; starting it initializes DB, laun… 6. **Tests** — `cargo test` reports 33 passed, 0 failed, 7 ignored
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 6 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.
- 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.
- A quick evaluation: it was running 6 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/bili-sync)Questions
- Does bili-sync run?
- Yes. bili-sync runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test bili-sync?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cc9a77aa4934. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test bili-sync?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does bili-sync take to install?
- 6 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 bili-sync need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing bili-sync?
- 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 bili-sync?
- 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.