recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity
804 Commits 32 Branches 1 Tag
1ba0d961a39d8bb73726138fb580bec554c45444
Commit Graph
6 Commits
Author SHA1 Message Date
autonomic-bot 1ba0d961a3 test(plausible): pin UPGRADE_BASE_VERSION to 3.0.1+v2.0.0 (newest published)
continuous-integration/drone/push Build is failing
Details 
The harness default base (recipe_versions[-2]) resolves to 3.0.0+v2.0.0 for
the open 3.1.0 upgrade PR. That release predates x86_64 support in the
clickhouse entrypoint (added 3.0.1): on this amd64 host it downloads
clickhouse-backup-linux-x86_64.tar.gz — a deterministic HTTP 404 — and with
set -e + a silenced wget the container exits 1 before logging anything,
crash-looping until the deploy times out. The base therefore can never
converge, regardless of the PR content (the published tag is immutable).

This is exactly the case the harness documents for UPGRADE_BASE_VERSION:
a PR adding its version ABOVE the newest published tag, where the true
predecessor is [-1] (3.0.1+v2.0.0), not [-2]. The upgrade tier then tests
the real operator path 3.0.1 -> 3.1.0.

Pairs with recipe-maintainers/plausible#3 (its !testme can only go green
once this lands).
 2026-06-09 19:24:21 +00:00
autonomic-botandClaude Opus 4.8 b4f39cb51a fix(2): plausible install overlay — assert /api/health subsystems, not / (auth_controller 500s under headless DISABLE_AUTH; / is not a valid readiness probe) 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-29 18:13:20 +01:00
autonomic-botandClaude Opus 4.8 3943cd80e5 feat(2): Q4.7 plausible — §4.3 event-tracking functional tests + PARITY.md; /api/health readiness probe 
- functional/test_event_tracking.py: 2 recipe-specific tests (P3) — register site → POST /api/event
  (browser UA) → read back from clickhouse events_v2. test_pageview_event_roundtrip asserts stored
  name/pathname/hostname; test_custom_event_roundtrip asserts a custom-named goal lands under that name.
- test_health_check.py: probe /api/health (200, asserts clickhouse+postgres+sites_cache ready) — fixes
  the broken/unterminated docstring from the prior WIP edit; / is unreliable (500 init / 302 ready).
- recipe_meta.py: HEALTH_PATH=/api/health, HEALTH_OK=(200,); comment corrected.
- PARITY.md: P2 vacuous (no recipe-maintainer corpus); documents P3/P4 coverage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-29 18:05:16 +01:00
autonomic-botandClaude Opus 4.8 baae41fe10 fix(2): plausible HTTP_TIMEOUT 600→1200 + DEPLOY_TIMEOUT 1200 — app 500s until clickhouse/migrations ready 
v1 failed wait_healthy 'not healthy / (last status 500)': plausible's app starts before clickhouse
(plausible_events_db) is ready (recipe depends_on names events_db, mismatched → no swarm ordering) and
returns 500 until DB migrations finish (several min on cold deploy). It serves 302 once ready; widen
the health window.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-29 16:34:11 +01:00
autonomic-botandClaude Opus 4.8 f0f6b6f545 feat(2): Q4.7 plausible — ops + lifecycle overlays (postgres ci_marker; pg_dump backup hook) 
plausible (analytics; app + postgres db + clickhouse events_db). recipe_meta stub (DISABLE_AUTH/
REGISTRATION + SECRET_KEY_BASE) + health test pre-existing. Added ops.py (postgres ci_marker via db
service, container-env psql) + test_install/upgrade/backup/restore overlays. plausible's postgres has a
real pg_dump backup/restore hook (so P4 marker survives, unlike immich). §4.3 event-tracking test next
(after live-API discovery). Tags annotated.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-29 16:21:15 +01:00
autonomic-botandClaude Opus 4.7 5832da4fd1 deferred(2): Q4.7 plausible — drafted but 500 on cold-start, defer for operator-iterate 
tests/plausible/recipe_meta.py + tests/plausible/functional/test_health_check.py drafted with
EXTRA_ENV setting required Phoenix vars (DISABLE_AUTH, DISABLE_REGISTRATION, SECRET_KEY_BASE).
Stack converges 1/1 but the served app returns HTTP 500 from / for the full 600s HTTP_TIMEOUT
window — config-class failure, not a deploy-timing issue. Diagnosing needs live container-log
inspection + iterative env tuning, more debug cycles than fit autonomous mode. Committing the
draft + a DEFERRED.md entry; operator can iterate when they want.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-28 17:39:36 +01:00