enqueue-bundle

[READ-ONLY] Message queue bundle for Symfony. RabbitMQ, Amazon SQS, Redis, Service bus, Async events, RPC over MQ and a lot more

Runssource: GitHubhomepagePHPMITcommit 688851f8049e

PHP, MIT licensed. The project labels itself: amqp, bundle, job queue, message bus, message queue, php, rabbitmq and stomp.

enqueue-bundle runs. An Argusic agent installed it in 34 minutes and hit 8 errors on a clean machine with no GPU, and the whole session was recorded.

composer install completed with 152 packages; unit suite passes 87/87 and functional suite passes 38/38 using the file transport with real message send/consume/ack; the Symfony console app boots and enqueue:setup-broker prints 'Broker set up'.

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 97.5 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
97.5 / 100
cost of the verifying run
$0.58 (measured)
recorded runs
1
last tested
stars
274
forks
30
open issues
0
watchers
6
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 enqueue-bundle, 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.

  • composer could not download dist zips (no zip extension/unzip/7z)6 minutes
  • PHP runtime not installed in container5 minutes
  • PHP built --disable-phar; composer.phar refused to run4 minutes
  • composer resolution failed: require-dev needs ext-amqp/ext-mongo/ext-mongodb3 minutes
  • Functional tests errored: SimpleXML/PDO/sqlite missing and DOCTRINE_DSN unset3 minutes
  • Unit tests errored: DMS\PHPUnitExtensions\ArraySubset\Assert not found2 minutes
Install time
34 minutes
Cold machine to finish
35 minutes
Errors hit and fixed
8 hit, 7 fixed with no human help
How the result was proved
phpunit Tests/Unit exited 0: OK (87 tests, 153 assertions); phpunit Tests/Functional (excluding the 2 /var-guard tests) exited 0: OK (38 tests, 85 assertions) and logged 'Received from enqueue.app_name...test ... Processed ... ack'; console.php --version returned 'Symfony v7.4.21 (env: test, debug: true)'
Model tokens used
789,160
Exact commit tested
688851f8049e
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: `Tests/Functional/App/console.php --version` → `Symfony v7.4.21 (env: test, debug: tr…
- Repo changes: `composer.json` gained `dms/phpunit-arraysubset-asserts` dev dep + `config.platform…
tokens used
789,160
All work is complete and verified. Final report:
**What was done**
- No PHP existed in the container (no root, no apt install). I extracted Ubuntu `php8.3-*` debs int…
- `composer install --prefer-source` (zip/unzip missing) installed 152 packages successfully.
- Unit suite: `OK (87 tests, 153 assertions)`.
- Functional suite: `OK (38 tests, 85 assertions)` with `DOCTRINE_DSN=sqlite:///:memory:` and `AMQP…
- App launch: `Tests/Functional/App/console.php --version` → `Symfony v7.4.21 (env: test, debug: tr…
- Repo changes: `composer.json` gained `dms/phpunit-arraysubset-asserts` dev dep + `config.platform…

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 34 minutes.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Hit 8 errors during setup, 1 of which were not solved.
  • 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.

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/3Runs97.500.58

Topics (from GitHub)

amqpbundlejob-queuemessage-busmessage-queuephprabbitmqstompsymfonysymfony-bundle

Embed the badge

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

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

Questions

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