nsq

A realtime distributed messaging platform

Runssource: GitHubhomepageGoMITcommit 85cf10c09c6c

Go, MIT licensed. The project labels itself: distributed systems, go, message queue, messaging, nsq and queue.

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

NSQ v1.3.0 builds on Go 1.26.8, all 11 test packages pass (0 failures), and nsqlookupd+nsqd boot, accept HTTP publishes, and deliver messages end-to-end.

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.03 (measured)
recorded runs
1
last tested
stars
25,779
forks
2,885
open issues
78
watchers
821
size
14 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 nsq, 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 binary not found in PATH5 minutes
  • Go 1.25.0 had Swiss-map internal redeclaration compiler errors2 minutes
Install time
7 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test -timeout 90s ./... exited 0 (all packages passed); curl -w '%{http_code}' -d 'hello' http://127.0.0.1:4151/pub?topic=test returned 200; stats endpoint confirmed 'message_count': 1 and 'health': 'OK'
Model tokens used
168,721
Exact commit tested
85cf10c09c6c
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.

                "percentiles": null
            }
        }
    ],
    "memory": {
All working. The stats JSON confirms `"message_count": 1`, `"depth": 1`, and `"health": "OK"`. Real…
Let me clean up and compile the report
exec
/bin/sh -lc 'pkill -9 nsqlookupd nsqd 2>/dev/null; true' in /work/repo
 succeeded in 0ms:
tokens used
168,721

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 7 minutes.
  • Recovered from all 2 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 7 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

distributed-systemsgomessage-queuemessagingnsqqueue

Embed the badge

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

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

Questions

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