due
A High-Performance Distributed Game Server Framework in Go
Runssource: GitHubhomepageGoMITcommit 806892f51b0b
Go, MIT licensed. The project labels itself: actor, actor framework, consul, distributed framework, distributed game framework, distributed systems, due and etcd.
due runs. An Argusic agent installed it in 5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Build succeeds with go build ./... all 33 test packages pass with zero failures, transporter gate/node builder tests run against live TCP servers.
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 93.3 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.
- Go 1.27.2 was not installed in the container1 minute
- sonic v1.14.2 has no build constraints for Go 1.27 (only go1.24 and !go1.26)1 minute
- config_test.go and config/file/config_test.go failed: stat ./config: no such file or directory1 minute
- lock_test.go: nil pointer dereference because no Maker was set1 minute
- internal/transporter/gate/builder_test.go: dial tcp 127.0.0.1:49899: connection refused1 minute
- internal/transporter/node/builder_test.go: dial tcp 127.0.0.1:49898: connection refused1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- go test -count=1 ./... exited 0 with all 50+ packages passing (0 failures)
- Model tokens used
- 175,214
- Exact commit tested
- 806892f51b0b
- 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.
core/buffer/reader.go:356:18: method ReadRune(order binary.ByteOrder) (rune, error) should have sig… container.go:107:3: misuse of unbuffered os.Signal channel as argument to signal.Notify container.go:109:3: misuse of unbuffered os.Signal channel as argument to signal.Notify log/internal/string_test.go:133:4: result of fmt.Sprintf call not used Those are all pre-existing issues in the codebase, not introduced by my changes. Let me verify: exec /bin/sh -lc 'cd /work/repo && export PATH="/home/runner/go/bin:$PATH" && export GOPATH="/home/runne… succeeded in 97ms: All fixed and verified. Let me compile the final report. tokens used 175,214 All fixed and verified. Let me compile the 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 5 minutes.
- Recovered from all 6 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 5 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)
actoractor-frameworkconsuldistributed-frameworkdistributed-game-frameworkdistributed-systemsdueetcdgamegame-enginegame-frameworkgame-servergogo-frameworkgrpckcpnacosrpcxtcpwebsocket
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/due)Questions
- Does due run?
- Yes. due runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test due?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 806892f51b0b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test due?
- 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 due take to install?
- 5 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 due need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing due?
- 6 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.
- Where is the evidence for due?
- 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.