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 20 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Mint v1.11.0 compiled with Elixir 1.15.0 on Erlang/OTP 25; 656 of 659 offline tests pass; 3 IPv6-dependent tests fail because the container has IPv6 disabled. Dependencies (castore, hpax, dialyxir, excoveralls, mox, stream_data, ex_doc, ect) all fetched and compiled.

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.10 (measured)
recorded runs
2
last tested
stars
1,419
forks
132
open issues
16
watchers
26
size
1 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 mint, 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.

  • No Erlang/OTP or Elixir installed in container - apt debs required root so had to extract manually8 minutes
  • Elixir 1.14 from apt too old - mint requires ~> 1.153 minutes
  • Missing parsetools include files (leexinc.hrl, yeccpre.hrl) needed by earmark_parser dependency2 minutes
  • 3 IPv6 test failures (test/transport/tcp_test.exs and ssl_test.exs)
Install time
20 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
mix test --exclude requires_internet_connection --no-compile exited 2; 659 tests, 3 failures, 52 excluded, 2 doctests, 9 properties
Model tokens used
116,018
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.

/work/repo/erlang-ssh_1%3a25.3.2.8+dfsg-1ubuntu4.8_amd64.deb
/work/repo/erlang-ssl_1%3a25.3.2.8+dfsg-1ubuntu4.8_amd64.deb
/work/repo/erlang-syntax-tools_1%3a25.3.2.8+dfsg-1ubuntu4.8_amd64.deb
/work/repo/erlang-tftp_1%3a25.3.2.8+dfsg-1ubuntu4.8_amd64.deb
/work/repo/erlang-tools_1%3a25.3.2.8+dfsg-1ubuntu4.8_amd64.deb
/work/repo/erlang-xmerl_1%3a25.3.2.8+dfsg-1ubuntu4.8_amd64.deb
/work/repo/erlang_1%3a25.3.2.8+dfsg-1ubuntu4.8_all.deb
---found---
Now let me compute the timing for the report.
tokens used
116,018
Now let me compute the timing for the 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.
  • 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 20 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.

Of the 7 elixir projects Argusic has installed and timed, mint was the 6th fastest to reach a running state, and 7 of 7 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 Runner2/3Runs100.000.10
Argusic Runner1/3Runs100.000.05

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.

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

Questions

Does mint run?
Yes. mint runs. Argusic installed and launched it on a clean machine in 20 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. 2 attempts are 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.10: 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?
20 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 7 elixir projects Argusic has installed and timed, mint was the 6th fastest to reach a running state, and 7 of 7 reached one at all.
Where is the evidence for mint?
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.

Discussion