function-mesh

The serverless framework purpose-built for event streaming applications.

Runssource: GitHubhomepageGoApache-2.0commit a2cb1ca50b63

Go, Apache-2.0 licensed. The project labels itself: apache pulsar, connectors, event streaming, pulsar functions, pulsar io, serverless and stream processing.

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

Go 1.25.0 installed, project builds, controller test suite passes all 57 specs using real Kubernetes envtest binaries

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.09 (measured)
recorded runs
1
last tested
stars
227
forks
31
open issues
36
watchers
29
size
58 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 function-mesh, 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 Go compiler found in environment1.5 minutes
  • envtest binaries missing at /usr/local/kubebuilder/bin/ (etcd, kube-apiserver, kubectl)0.5 minutes
Install time
2 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test ./controllers/ -v exited 0, PASS, 57/57 specs passed in 14.65s; go build -o bin/function-mesh-controller-manager main.go produced binary; binary --help printed all CLI flags; go test passed license check
Model tokens used
77,403
Exact commit tested
a2cb1ca50b63
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.

**App launch**: The `function-mesh-controller-manager --help` command succeeded, listing all CLI fl…
tokens used
77,403
Here's the summary of what happened:
**Initial state**: No Go installed, no Go binaries on PATH. The project is a Kubernetes operator (F…
**Installed Go**: Downloaded Go 1.25.0 from go.dev and extracted to `/tmp/golang/go/bin/go`.
**Build succeeded**: `go build -o bin/function-mesh-controller-manager main.go` produced a 72MB bin…
**Test setup issue**: The controller tests (Ginkgo BDD suite) required `etcd` and `kube-apiserver` …
**Tests pass**:
- `go test` (license test): **PASS** (0.02s)
- `go test ./controllers/` (57 specs, Suite: Controller Suite): **PASS** (14.65s, 57 of 57 specs ra…
**App launch**: The `function-mesh-controller-manager --help` command succeeded, listing all CLI fl…

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 1.5 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 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 1.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.09

Topics (from GitHub)

apache-pulsarconnectorsevent-streamingpulsar-functionspulsar-ioserverlessstream-processing

Embed the badge

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

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

Questions

Does function-mesh run?
Yes. function-mesh runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test function-mesh?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a2cb1ca50b63. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test function-mesh?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does function-mesh take to install?
1.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 function-mesh need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing function-mesh?
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 function-mesh?
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