ecommerce_api

E-commerce by Django Rest Framework

Could not verifysource: GitHubPythonMITcommit ce65724cf3ca

Python, MIT licensed. The project labels itself: django, django rest framework, ecommerce, ecommerce api, python and restful api.

Argusic could not get ecommerce_api running. An Argusic agent installed it in 47 minutes and hit 24 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Django 5.1.3 project boots, migrations apply without errors, dev server answers 200 on root endpoint, all 356 requirements installed in venv

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

At a glance

verdict
Could not verify
Argusic Score
50 / 100
cost of the verifying run
$0.42 (measured)
recorded runs
2
last tested
stars
296
forks
98
open issues
3
watchers
2
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 ecommerce_api, 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.

  • mysqlclient==2.2.6 has no x86_64 Linux wheel and build fails without mysql headers5 minutes
  • PyJWT version conflict: djangorestframework-jwt requires <2.0, firebase-admin requires >=2.55 minutes
  • django-haystack version metadata broken on PyPI; pip reports '0.0.0'3 minutes
  • ugettext/ugettext_lazy removed in Django 5.x3 minutes
  • clyent==1.2.2 not found on PyPI2 minutes
  • Windows-only packages uninstallable (pywin32, comtypes, pyreadline, etc.)2 minutes
Install time
47 minutes
Cold machine to finish
48 minutes
Errors hit and fixed
24 hit, 24 fixed with no human help
How the result was proved
manage.py check passed (14 warnings only); manage.py migrate ran all migrations; runserver answered HTTP 200 on GET /
Model tokens used
2,248,248
Exact commit tested
ce65724cf3ca
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.

    {"msg": "elasticsearch-dsl 8.x incompatible with django-elasticsearch-dsl-drf", "fix": "downgra…
    {"msg": "googletrans uses removed httpcore.SyncHTTPTransport type", "fix": "patched to typing.A…
    {"msg": "rest_auth uses removed django.conf.urls.url", "fix": "patched to django.urls.re_path",…
    {"msg": "allauth.utils missing email_address_exists and get_username_max_length", "fix": "added…
  ],
  "test_depth": "tier3_none",
  "notes": "Project has only placeholder test stubs (3 lines each). Django admin and REST API pages…
  "verified_how": "manage.py check passed (14 warnings only); manage.py migrate ran all migrations;…
  "final_state": "Django 5.1.3 project boots, migrations apply without errors, dev server answers 2…
}
tokens used
2,248,248

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

  • Recovered from all 24 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, 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.
  • Took 47 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.

Of the 6 django projects Argusic has installed and timed, ecommerce_api was the 6th fastest to reach a running state, and 5 of 6 reached one at all.

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 Runner2/3Did not run20.000.17
Argusic Runner1/3Unverified80.000.42

Topics (from GitHub)

djangodjango-rest-frameworkecommerceecommerce-apipythonrestful-api

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/ecommerce_api.svg)](https://argusic.com/subject/ecommerce-api)

Questions

Does ecommerce_api run?
Argusic could not verify that ecommerce_api runs. Argusic installed and launched it on a clean machine in 47 minutes, hitting 24 errors on the way, and recorded the session.
How did Argusic test ecommerce_api?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ce65724cf3ca. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ecommerce_api?
The run that produced this verdict cost $0.42: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ecommerce_api take to install?
47 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 ecommerce_api need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ecommerce_api?
24 things broke in the recorded run, and 24 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ecommerce_api compare with the alternatives?
Of the 6 django projects Argusic has installed and timed, ecommerce_api was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
Where is the evidence for ecommerce_api?
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