armeria

Your go-to microservice framework for any situation, from the creator of Netty et al. You can build any type of microservice leveraging your favorite technologies, including gRPC, Thrift, Kotlin, Retrofit, Reactive Streams, Spring Boot and Dropwizard.

Runssource: GitHubhomepageJavaApache-2.0commit e118fd45af4e

Java, Apache-2.0 licensed. The project labels itself: gateway, grpc, grpc client, grpc server, hacktoberfest, http, http client and http server.

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

Armeria core module compiles and its full com.linecorp.armeria.common test suite (2239 tests) passes on JDK 21 with Gradle 9.6.1. The project also builds annotation-processor tests successfully.

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.19 (measured)
recorded runs
2
last tested
stars
5,148
forks
1,026
open issues
711
watchers
179
size
348 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 armeria, 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.

  • Error Prone plugin required JDK 21 (class file version 65.0)3 minutes
  • No JDK found in environment2 minutes
  • Error Prone on JDK 21 requires -XDaddTypeAnnotationsToSymbol=true compiler flag2 minutes
Install time
12 minutes
Cold machine to finish
63 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
./gradlew :core:test --tests 'com.linecorp.armeria.common.*' -PnoLint reported BUILD SUCCESSFUL; 2239 tests, 0 failures, 0 errors across 186 test classes
Model tokens used
304,680
Exact commit tested
e118fd45af4e
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.

1. **Environment setup**: No JDK was pre-installed. Downloaded Temurin JDK 21 (`/home/runner/jdk21`…
2. **Compilation fix**: Error Prone on JDK 21 requires `-XDaddTypeAnnotationsToSymbol=true`. Patche…
3. **Verification ran**: `:core:compileJava`, `:core:compileTestJava`, `:annotation-processor:test`…
**Unfixed issue**: Full `compileJava` across all subprojects fails on `:jetty9` due to a caffeine c…
tokens used
304,680
Here's the full summary of what happened and the final result.
**Actions taken:**
1. **Environment setup**: No JDK was pre-installed. Downloaded Temurin JDK 21 (`/home/runner/jdk21`…
2. **Compilation fix**: Error Prone on JDK 21 requires `-XDaddTypeAnnotationsToSymbol=true`. Patche…
3. **Verification ran**: `:core:compileJava`, `:core:compileTestJava`, `:annotation-processor:test`…
**Unfixed issue**: Full `compileJava` across all subprojects fails on `:jetty9` due to a caffeine c…

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 12 minutes.
  • Recovered from all 3 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 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.19
Argusic Runner1/3Ran out of time0.000.12

Topics (from GitHub)

gatewaygrpcgrpc-clientgrpc-serverhacktoberfesthttphttp-clienthttp-serverhttp2micro-frameworkmicroservicesnettyrpcrpc-clientrpc-frameworkrpc-libraryrpc-serverthriftthrift-clientthrift-server

Embed the badge

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

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

Questions

Does armeria run?
Yes. armeria runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test armeria?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e118fd45af4e. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test armeria?
The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does armeria take to install?
12 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 armeria need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing armeria?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for armeria?
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