dejavu
A Web UI for Elasticsearch and OpenSearch: Import, browse and edit data with rich filters and query views, create reference search UIs.
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 8b8f11f40cd6
JavaScript, MIT licensed. The project labels itself: appbaseio, chrome extension, database, database gui, dejavu, elasticsearch, elasticsearch gui and elasticsearch plugin.
dejavu runs, with stand-ins for the services it depends on. An Argusic agent installed it in 24 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
Dev server responds HTTP 200 on port 1358, production build compiles to dist/app/ (53 MiB), and 6 of 8 pre-compiled library tests pass
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 79.1 of 100 (the mean of this project's run scores).
At a glance
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.
- source tests in batteries submodule can't be transformed by Jest — no submodule babel config3 minutes
- favicons peer dependency requires Node >= 20.9.0, container has 18.19.12 minutes
- 2 mappings tests fail: batteries submodule updated updateMapping() (commit 50a23dc) but test expectations are stale
- Install time
- 24 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w '%{http_code}' http://localhost:1358/ returned 200; npx jest returned 6 passed, 2 failed (upstream batteries mismatch)
- Model tokens used
- 485,280
- Exact commit tested
- 8b8f11f40cd6
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
5. Built `dejavu-main` (the web app) — production build completed **Errors encountered and fixes:** | Error | Fix | Minutes | |---|---|---| | `yarn` command not found in container | Installed yarn via `npm install -g [email protected] --prefix … | `favicons` peer dependency missing during webpack build; needs Node >= 20.9.0 but container has N… | Source tests in `src/batteries/` fail with `SyntaxError: Cannot use import statement outside a mo… | 2 of 8 tests in `lib/batteries/__tests__/mappings.js` fail — the batteries submodule was updated … **Verification:** - **Dev server**: `webpack-dev-server` on port 1358 returns HTTP 200 - **Production build**: `webpack` compiles to `dist/app/` (53 MiB, includes main.js, common.js, run… - **Test suite**: `npx jest --testMatch '**/lib/batteries/**/__tests__/**/*.js'` — 1 suite passed (…
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
- Installed in 24 minutes.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 3 errors during setup, 1 of which were not solved.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 3/3 | Runs with mocks | 85.33 | 0.16 | |
| Argusic Runner | 2/3 | Runs with mocks | 72.00 | 0.12 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.06 |
Topics (from GitHub)
appbaseiochrome-extensiondatabasedatabase-guidejavuelasticsearchelasticsearch-guielasticsearch-pluginnosqlopensearchopensearch-pluginsreactreactjsrealtime-updates
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dejavu)Questions
- Does dejavu run?
- dejavu runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 24 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test dejavu?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8b8f11f40cd6. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test dejavu?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does dejavu take to install?
- 24 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 dejavu need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dejavu?
- 3 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 dejavu?
- All 3 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.