Acceptance test: use quak end to end as a user before a release candidate #237

New Issue

2026-11-11T20:55:31+01:00

clawbot commented

2026-11-11 20:55:31 +01:00

Hands-on test before a release candidate, by the top-level manager's standing practice (sneak asked on 10 November whether vaultik had been tested by hand; it had not, and sfdupes then showed missing basics on first real use).

What to do

Build next fresh with the repo's own entrypoints and use quak as a new user would, following README.md literally, every command and claim in it. Use small synthetic data in local containers; nothing RAM-heavy, and no real third-party accounts or credentials (stop and say so where one is needed).

Definition of done

Every defect filed as its own issue: steps, what happened, what should happen.
Every missing basic a user would expect filed as its own issue titled proposal: ..., assigned to sneak.
One comment here: a plain verdict (ready for a release candidate, or not), the issues filed, each marked defect or proposal, and anything in the README that turned out wrong. No code changes.

Model: opus-5-5

Hands-on test before a release candidate, by the top-level manager's standing practice (sneak asked on 10 November whether vaultik had been tested by hand; it had not, and sfdupes then showed missing basics on first real use). ## What to do Build `next` fresh with the repo's own entrypoints and use quak as a new user would, following `README.md` literally, every command and claim in it. Use small synthetic data in local containers; nothing RAM-heavy, and no real third-party accounts or credentials (stop and say so where one is needed). ## Definition of done - Every defect filed as its own issue: steps, what happened, what should happen. - Every missing basic a user would expect filed as its own issue titled `proposal: ...`, assigned to sneak. - One comment here: a plain verdict (ready for a release candidate, or not), the issues filed, each marked defect or proposal, and anything in the README that turned out wrong. No code changes. Model: opus-5-5

clawbot commented

2026-11-11 21:22:38 +01:00

Verdict: not ready. Three things stop it:

quak helper fix-missing-thumbnails fails on every file it tries to fix.
The README's first install step fails on Node 22 releases that the README says are supported.
The binary that the cron section installs can stop starting after nix garbage collection.

Issues filed

defect: fix-missing-thumbnails never uploads, because the upload lacks a header the upload URL signs: #238
defect: the stated Node minimum is wrong for both the Getting Started and the library install: #239
defect: the make install binary on Linux depends on a nix store path that nothing keeps: #240
defect: quak get and quak get-thumb list a --collection option that does nothing: #241
defect: the README does not say what a backup does with a photo deleted in Ente: #242
proposal: let the command line use a self-hosted Ente server: #243
proposal: say in words why a login failed, not just HTTP 401 or HTTP 404: #244
proposal: date each backup run's output, since the README's crontab appends every night to one log: #245

What the README gets wrong

"The commands below need git, Node 22 or later and yarn": yarn install needs Node 22.13, and "Using the library"'s yarn add file:../quak now needs 22.22.2.
The quak helper fix-missing-thumbnails section describes thumbnails being uploaded; no upload succeeds.

How it was run

next at 30fc349, built with yarn install, yarn build and make install.
The server was a local self-hosted Ente server in containers: Ente's server image, its web app, Postgres and MinIO-compatible storage.
The account was created and changed through Ente's web app in headless Chrome. It held synthetic images only.
Deviation: the command line has no server setting, which is the self-hosting proposal. It reached the local server through a local TLS proxy that answered for api.ente.io, files.ente.io and thumbnails.ente.io, with a test CA. The library used its apiOrigin option.
To run the README's library example past the Node defect, yarn add used --ignore-engines.

Not checked

Live photos and videos: the web app cannot make a live photo, and no video was generated.
Shared albums: they need a second account.
Login with an email code: not run. Login with a TOTP code was run.
macOS paths.
Ente's hosted service: not contacted, as this issue asks. That check stays with the live-account issue, #187.

Model: opus-5-5

**Verdict: not ready.** Three things stop it: - `quak helper fix-missing-thumbnails` fails on every file it tries to fix. - The README's first install step fails on Node 22 releases that the README says are supported. - The binary that the cron section installs can stop starting after nix garbage collection. ## Issues filed - defect: `fix-missing-thumbnails` never uploads, because the upload lacks a header the upload URL signs: https://git.eeqj.de/sneak/quak/issues/238 - defect: the stated Node minimum is wrong for both the Getting Started and the library install: https://git.eeqj.de/sneak/quak/issues/239 - defect: the `make install` binary on Linux depends on a nix store path that nothing keeps: https://git.eeqj.de/sneak/quak/issues/240 - defect: `quak get` and `quak get-thumb` list a `--collection` option that does nothing: https://git.eeqj.de/sneak/quak/issues/241 - defect: the README does not say what a backup does with a photo deleted in Ente: https://git.eeqj.de/sneak/quak/issues/242 - proposal: let the command line use a self-hosted Ente server: https://git.eeqj.de/sneak/quak/issues/243 - proposal: say in words why a login failed, not just `HTTP 401` or `HTTP 404`: https://git.eeqj.de/sneak/quak/issues/244 - proposal: date each backup run's output, since the README's crontab appends every night to one log: https://git.eeqj.de/sneak/quak/issues/245 ## What the README gets wrong - "The commands below need `git`, Node 22 or later and `yarn`": `yarn install` needs Node 22.13, and "Using the library"'s `yarn add file:../quak` now needs 22.22.2. - The `quak helper fix-missing-thumbnails` section describes thumbnails being uploaded; no upload succeeds. ## How it was run - `next` at `30fc349`, built with `yarn install`, `yarn build` and `make install`. - The server was a local self-hosted Ente server in containers: Ente's server image, its web app, Postgres and MinIO-compatible storage. - The account was created and changed through Ente's web app in headless Chrome. It held synthetic images only. - Deviation: the command line has no server setting, which is the self-hosting proposal. It reached the local server through a local TLS proxy that answered for `api.ente.io`, `files.ente.io` and `thumbnails.ente.io`, with a test CA. The library used its `apiOrigin` option. - To run the README's library example past the Node defect, `yarn add` used `--ignore-engines`. ## Not checked - Live photos and videos: the web app cannot make a live photo, and no video was generated. - Shared albums: they need a second account. - Login with an email code: not run. Login with a TOTP code was run. - macOS paths. - Ente's hosted service: not contacted, as this issue asks. That check stays with the live-account issue, https://git.eeqj.de/sneak/quak/issues/187. Model: opus-5-5

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/quak#237