tms

基于频道模式的团队沟通协作+轻量级任务看板,支持mardown、富文本、在线表格和思维导图的团队博文wiki,i18n国际化翻译管理的响应式web开源团队协作系统。

Runssource: GitHubhomepageJavaScriptMITcommit d50a870a876c

JavaScript, MIT licensed. The project labels itself: blog, chat, chinese, excel, gantt, gitter, group and kanban.

tms runs. An Argusic agent installed it in 17 minutes and hit 7 errors on a clean machine with no GPU, and the whole session was recorded.

TMS Spring Boot app compiles and runs on port 8080 with MySQL 5.7.44 backend; 27 of 33 tests pass.

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

At a glance

verdict
Runs
Argusic Score
97.1 / 100
cost of the verifying run
$0.44 (measured)
recorded runs
1
last tested
stars
389
forks
109
open issues
5
watchers
26
size
133 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 tms, 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.

  • MySQL not available — no mysqld or docker6 minutes
  • Java 8 (javac/java) not found in environment1 minute
  • Maven (mvn) not found in environment1 minute
  • spring.profiles.active invalid in profile-specific test properties file (SB 2.4+ regression)1 minute
  • Missing tms.blog.md2pdf.path placeholder in test config1 minute
  • SecurityConfig @Profile excluded test profile; test context loaded with no security1 minute
Install time
17 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
7 hit, 6 fixed with no human help
How the result was proved
curl -s -o /dev/null -w %{http_code} http://127.0.0.1:8080/ returned 200; mvn test ran 33 tests, 27 passed, contextLoads test passed
Model tokens used
669,142
Exact commit tested
d50a870a876c
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.

tokens used
669,142
Here's a summary of everything done and the final report.
**Work completed:**
- Installed Java 8 (Temurin JDK) and Maven 3.9.9 from binaries
- Downloaded & configured MySQL 5.7.44 (with missing libaio library) — initialized, started on port…
- Fixed `application-test.properties` (invalid `spring.profiles.active` in profile-specific resourc…
- Fixed SecurityConfig `@Profile` annotations to include `test`
- Added missing `tms.blog.md2pdf.path` property to test config
- Build: `mvn compile` and `mvn package` both succeed
- App launch: starts on port 8080, HTTP 200 on `/`
- Tests: 27 of 33 pass; 6 pre-existing failures from hardcoded developer machine paths

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.
  • 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

  • Took 17 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.
  • Hit 7 errors during setup, 1 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 11 blog projects Argusic has installed and timed, tms was the 11th fastest to reach a running state, and 11 of 11 reached one at all.

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/3Runs97.140.44

Topics (from GitHub)

blogchatchineseexcelganttgittergroupkanbanmarkdownresponsive-designslackteamworktmstranslatetranslationwebchatwiki

Embed the badge

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

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

Questions

Does tms run?
Yes. tms runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test tms?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d50a870a876c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test tms?
The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tms take to install?
17 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 tms need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tms?
7 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.
How does tms compare with the alternatives?
Of the 11 blog projects Argusic has installed and timed, tms was the 11th fastest to reach a running state, and 11 of 11 reached one at all.
Where is the evidence for tms?
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