5 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
autonomic-bot	f5f11cd769	chore(rustdesk): drop unused import	2026-10-30 19:03:11 +00:00
autonomic-bot	1653582764	fix(rustdesk): punch-hole version gate via deployed_identity (loud on unparsable, skip <1.1.16)	2026-10-30 19:02:58 +00:00
autonomic-bot	d71a53cb62	enroll(rustdesk-server): test suite + bridge poll (status-key overlay, ws + punch-hole-amplification tests)	2026-10-30 18:58:43 +00:00
autonomic-bot	79c652ddd3	test(plausible): psql -q in _register_site — -t does not suppress command tags ... psql -tAc still prints INSERT/CREATE command tags (e.g. "INSERT 0 1"), so _register_site asserted out == site against "INSERT 0 1\nsite" and both event-tracking roundtrip tests failed on their very first run (build 237 — the custom tier had never executed before; install always failed earlier). -q suppresses the tags; verified against the recipe db container.	2026-06-09 22:50:55 +00:00
autonomic-bot	1ba0d961a3	test(plausible): pin UPGRADE_BASE_VERSION to 3.0.1+v2.0.0 (newest published) ... 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