gel
Gel supercharges Postgres with a modern data model, graph queries, Auth & AI solutions, and much more.
Not yet verifiedsource: GitHubhomepagePythonApache-2.0commit 85191063b4db
Python, Apache-2.0 licensed. The project labels itself: database, edgedb, edgeql, gel, graph relational, high performance and relational database.
gel has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 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 most recent recorded attempt, which did not reach a 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.
- PostgreSQL build fails: ICU library not found, then readline, then flex not in PATH, then bison not propagated correctly12 minutes
- Python.h and pyconfig.h not found (no python3.12-dev package); C extension compilation fails6 minutes
- Git submodules (postgres, pgproto, libpg_query) not initialized; 'edb/server/pgproto/uuid.pyx' and other paths missing2 minutes
- protobuf-c/protobuf-c.h not found for libpg_query C extension2 minutes
- No git tags in repo; buildmeta.get_version_from_scm fails with ValueError: max() iterable argument is empty1 minute
- Install time
- 64 minutes
- Cold machine to finish
- 25 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- python -m unittest tests.test_edgeql_syntax tests.test_api_errors tests.edgeql.test_quote tests.test_docs tests.common.test_* -v returned 824 OK (skipped=22, expected failures=2); gel-server --help prints option list; python -c "import edb.server._rust_native; import edb.common.turbo_uuid" loads Rust/C extensions
- Model tokens used
- 908,061
- Exact commit tested
- 85191063b4db
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Attempt postgres build (failed): 8 min - Final verification: 4 min Total: ~64 min Time to compile the report: exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1790440795 Here is the final report: tokens used 908,061 Here is the final report:
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.
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 | 1/3 | Unverified | 80.00 | 0.18 |
Topics (from GitHub)
databaseedgedbedgeqlgelgraph-relationalhigh-performancerelational-database
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gel)Questions
- Does gel run?
- gel has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test gel?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for gel?
- 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.