sdk-java

Temporal Java SDK

Runssource: GitHubhomepageJavaApache-2.0commit 8d2f35e7d90d

Java, Apache-2.0 licensed. The project labels itself: durable execution, framework, java, java sdk, microservices, open source, orchestration and temporal sdk.

sdk-java runs. An Argusic agent installed it in 5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Temporal Java SDK compiles, passes spotlessCheck, and all non-cloud tests pass across temporal-sdk, temporal-test-server, temporal-testing, temporal-kotlin, temporal-spring-boot-autoconfigure, and temporal-serviceclient subprojects.

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.23 (measured)
recorded runs
1
last tested
stars
445
forks
276
open issues
264
watchers
16
size
16 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.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • CancelWorkflowAsyncOperationTest.cancelAsyncOperationAbandon fails in container — requires cloud Nexus provisioning
Install time
5 minutes
Cold machine to finish
71 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
./gradlew :temporal-sdk:test --tests 'io.temporal.workflow.*' etc, 1093 tests completed, 1 cloud-only failure, 165 skipped; :temporal-test-server:test, :temporal-testing:test, :temporal-kotlin:test, :temporal-spring-boot-autoconfigure:test all BUILD SUCCESSFUL
Model tokens used
312,907
Exact commit tested
8d2f35e7d90d
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

tokens used
312,907
Here is my complete report.
**Install**: No Java was available in the container. Downloaded JDK 21 (Temurin-21.0.12.1) from Ado…
**Tests verified**:
- `:temporal-sdk:test` — **1093 tests completed, 165 skipped, 1 failed**. The sole failure (`Cancel…
- `:temporal-test-server:test` — All passed
- `:temporal-testing:test` — All passed
- `:temporal-kotlin:test` — All passed
- `:temporal-spring-boot-autoconfigure:test` — All passed
- Individual workflow/activity/client test classes all passed
**Full `./gradlew build`** timed out in the container (build includes the full test suite which tak…

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 1 error 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.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.23

Topics (from GitHub)

durable-executionframeworkjavajava-sdkmicroservicesopen-sourceorchestrationtemporal-sdkworkflow-automationworkflow-engineworkflow-tool

Embed the badge

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

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

Questions

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