fix: repair 2.0 demo setup after release stamp - #140
Conversation
NikolayS
left a comment
There was a problem hiding this comment.
samorev-spec-assisted review
Reviewed corrected head 036469d52087aa12fe4b136faa92cac309765431 by applying the samorev specialist specifications directly.
Code review
- Bug Hunter:
NO_FINDINGS - Security Reviewer:
NO_FINDINGS - Documentation Reviewer:
NO_FINDINGS - Guidelines Checker:
NO_FINDINGS - Test Analyzer:
NO_FINDINGS - Sqitch Migration Checker: not applicable; this repository is not Sqitch-enabled
The implementation review found no blocking or non-blocking code findings. Installer discovery, readiness/error propagation, smoke validation, recorder cleanup, workload signal handling, and the refreshed demo documentation are internally consistent at this head.
Manual and local evidence
This evidence is separate from the code-review verdict and hosted CI:
- exact-head positive Postgres 18 Docker smoke passed with
2.0-beta1, pg_cron, one sampler job, and live samples - exact-head missing-installer smoke failed in 8 seconds with the expected diagnostics
bash -n, ShellCheck, workflow parsing, demo prerequisite checks, andgit diff --checkpassed- a full default
make -C demos recordcompleted end to end - the refreshed cast is 48,256 bytes/1,162 lines, starts at
0.0, shows2.0-beta1and UTC timestamps, and contains noERROR,FATAL, orPANIC - the GIF is 419,214 bytes, 867 frames, and 1020 × 462 pixels
- seven representative frames were inspected at original resolution; the banner/status, periods, colored chart/legend, AAS drilldowns, query drill, and closing diagnosis are readable and aligned
- the final workload cleanup correction preserves command/signal status; the exact-head smoke checks passed after that correction
Hosted CI
For the exact reviewed head, GitHub reported 12 successful checks and 0 pending, failing, cancelled, or skipped checks: CodeQL, docs lint, demo smoke, PG14–PG19 beta cron-on, and PG17 cron-off.
Gate status
This is a COMMENT review, not an approval. Explicit owner approval is still absent. The pull request remains draft and must not be merged or marked ready until the owner provides that approval.
Closes #138
Summary
ash_sql_chain.pyinstead of the removeddevel/sql/ash-install.sqlIFS, noninteractive Postgres commands, and reliable cleanupASH_CRON_OPTIONALguidanceRoot cause
The 2.0 beta release stamp moved the fresh installer from
devel/sql/tosql/, while the demo entrypoint retained the removed development path. The detached recorder also had no readiness handshake, so setup could fail immediately and the host would still enter the full warmup.Validation
At corrected head
036469d:origin/main:/repo/devel/sql/ash-install.sqlwas missingmake -C demos smoke: passed with version2.0-beta1, pg_cron available, exactly one sampler job, and a live sampleASH_INSTALL_SQL=/repo/does-not-exist.sql make -C demos smoke: failed in 8 seconds, reportedpg_ash installer not readable, and surfaceddemo setup exited before readinessmake -C demos record: passed end to end, including the Docker build, 330-second warmup, live recording,aggrendering, andgifsicleoptimizationbash -n demos/*.shshellcheck -x demos/*.shactionlint -shellcheck ''make -C demos checkgit diff --check036469d: 12 passed, with none pending, failing, cancelled, or skippedRefreshed artifacts
demos/ash_demo.cast: 48,256 bytes, 1,162 lines, first event at0.0, current2.0-beta1status, UTC+00timestamps, and noERROR,FATAL, orPANICdemos/ash_demo.gif: 419,214 bytes, 867 frames, 1020 × 462 pixelsSeven representative GIF frames were inspected at original resolution. The opening banner and status, periods table, zero-based colored chart and legend, wait-event AAS/backend-seconds/percentage output, query drill, and closing diagnosis are readable, aligned, and fit the recording geometry.
The pull request intentionally remains draft.