siddhi

Stream Processing and Complex Event Processing Engine

Could not verifysource: GitHubhomepageJavaApache-2.0commit e1da9b7f3cd7

Java, Apache-2.0 licensed. The project labels itself: cep, cloud, cloud native, cncf, complex event processing, library, online learning and stream processing.

Argusic could not get siddhi running. An Argusic agent hit no errors on a clean machine with no GPU, and the whole session was recorded.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Could not verify
Argusic Score
not scored yet
cost of the verifying run
$0.29 (measured)
recorded runs
2
last tested
stars
1,594
forks
528
open issues
125
watchers
112
size
35 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.

Exact commit tested
e1da9b7f3cd7
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.

Install time
the run did not report one
Cold machine to finish
the attempt was stopped at the time limit after 87 minutes, so it never finished
Errors hit and fixed
the attempt was cut off at the time limit before it reported what it had hit
How the result was proved
runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Model tokens used
not recorded for this run
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
Whether it works at all
the attempt did not get far enough to verify anything before the time limit

The end of the recording

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

        Assert.assertEquals(response.getStatus(), 200, "HTTP 200 should be returned");
        Assert.assertTrue(response.getEntity().toString().contains("Siddhi app is deployed and runt…
                "Siddhi App creation message should be returned");
        Response undeployResponse = apiService.siddhiArtifactUndeploySiddhiAppGet("filterTest1");
        Assert.assertEquals(undeployResponse.getStatus(), 200, "HTTP 200 should be returned");
        Assert.assertTrue(undeployResponse.getEntity().toString().contains("Siddhi app removed succ…
                "Siddhi App removed message should be returned");
    }
}
Let me try running the full test suite one more time to get a clean summary from scratch, and also …
exec
/bin/sh -lc 'export JAVA_HOME=$HOME/tools/java && export PATH=$JAVA_HOME/bin:$HOME/tools/maven/bin:…

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

  • Nothing broke on the way: zero errors between clone and running.
  • 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

  • An agent with no time limit did not get it running.

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.

  • fluvio tested, not verified · Rust · 3 shared topics
  • vector verified to run · Rust · 2 shared topics
  • nats-server verified to run · Go · 2 shared topics
  • encore verified to run · Go · 2 shared topics
  • mirrord verified to run · Rust · 2 shared topics
  • riko verified to run · Python · 2 shared topics

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Ran out of time0.000.29
Argusic Runner1/3Ran out of time0.000.32

Topics (from GitHub)

cepcloudcloud-nativecncfcomplex-event-processinglibraryonline-learningstream-processingstreaming-data-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/siddhi.svg)](https://argusic.com/subject/siddhi)

Questions

Does siddhi run?
Argusic could not verify that siddhi runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.
How did Argusic test siddhi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e1da9b7f3cd7. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test siddhi?
The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
Does siddhi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing siddhi?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for siddhi?
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