panel-graphic-walker

A project providing a Graphic Walker Pane for use with HoloViz Panel.

Runssource: GitHubhomepagePythonMITcommit 2a892dc62b3e

Python, MIT licensed. The project labels itself: business intelligence, data, data analysis, data app, data exploration, data mining, data visualization and eda.

panel-graphic-walker runs. An Argusic agent installed it in 10 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Panel Graphic Walker package installs in a Python 3.12 venv with a pre-compiled JS bundle (4.2 MB), the test suite passes (149/149), and a Panel server serves a GraphicWalker app returning HTTP 200.

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.07 (measured)
recorded runs
1
last tested
stars
351
forks
14
open issues
11
watchers
7
size
11 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 panel-graphic-walker, 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.

  • hatchling build hook requires esbuild and fails with npm peer dependency conflict (@kanaries/graphic-walker requires react>=19.0.0 but panel pins [email protected])6 minutes
  • ModuleNotFoundError: editables, ibis-framework, aiohttp1 minute
  • Externally managed Python environment blocks system-wide pip install0.5 minutes
  • test_graphic_walker_apps.py: exec_with_return does not set __file__, causing NameError in examples using Path(__file__).parent
Install time
10 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
pytest tests/ --ignore=tests/test_graphic_walker_apps.py exited 0 with 149 passed, 1 xfailed, 6 xpassed; panel serve returned HTTP 200
Model tokens used
425,828
Exact commit tested
2a892dc62b3e
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.

All comprehensive tests passed!
exec
/bin/sh -lc 'echo "Start: 19:15, End: $(date +%H:%M)"' in /work/repo
 succeeded in 0ms:
Start: 19:15, End: 19:25
Here is my final report.
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 10, "errors": [{"msg": "Ex…
tokens used
425,828

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 10 minutes.
  • Recovered from all 4 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 MIT, 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 10 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.07

Topics (from GitHub)

business-intelligencedatadata-analysisdata-appdata-explorationdata-miningdata-visualizationedaholoviz-panellow-codenotebookpivot-tablepythontableautableau-alternativevegavega-litevisualization

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/panel-graphic-walker.svg)](https://argusic.com/subject/panel-graphic-walker)

Questions

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