mint
Functional HTTP client for Elixir with support for HTTP/1 and HTTP/2 馃尡
Runssource: GitHubElixirApache-2.0commit fb850d3714e4
Elixir, Apache-2.0 licensed. The project labels itself: elixir, elixir http, elixir lang, elixir language, http, http client and http2.
mint runs. An Argusic agent installed it in 10 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Erlang OTP 25 + Elixir 1.18.3 installed locally; Mint project compiles and its test suite runs 659 tests with 3 IPv6 failures caused by the container's kernel-level IPv6 disablement.
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.
- Erlang/OTP not installed (no erl, elixir, or mix in PATH)5 minutes
- Elixir not installed (Ubuntu version 1.14 but project requires ~> 1.15)2 minutes
- Test suite failed to start: could not find application file: tools.app1 minute
- Test suite failed to start: could not find application file: xmerl.app1 minute
- Install time
- 10 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- mix test --exclude requires_internet_connection --exclude proxy exited 0 with 2 doctests, 9 properties, 659 tests, 3 failures (all IPv6), 52 excluded
- Model tokens used
- 92,877
- Exact commit tested
- fb850d3714e4
- 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.
2 doctests, 9 properties, 659 tests, 3 failures, 52 excluded Now I have all the data. Let me clean up any stale session and produce the final report exec /bin/sh -lc 'export PATH="/home/runner/.local/bin:$PATH" export ROOTDIR="/home/runner/.local/prefix/usr/lib/erlang" cd /work/repo mix compile --no-deps-check 2>&1 | tail -3' in /work/repo succeeded in 1480ms: All done. Let me produce the final result. tokens used 92,877 All done. Let me produce the final result.
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 10 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Recovered from all 4 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 Apache-2.0, 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.
Of the 4 elixir projects Argusic has installed and timed, mint was the 2nd fastest to reach a running state, and 4 of 4 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.
- A quick evaluation: it was running 10 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)
elixirelixir-httpelixir-langelixir-languagehttphttp-clienthttp2
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mint)Questions
- Does mint run?
- Yes. mint runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test mint?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fb850d3714e4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mint?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mint take to install?
- 10 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 mint need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mint?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mint compare with the alternatives?
- Of the 4 elixir projects Argusic has installed and timed, mint was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for mint?
- 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.