YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
Rust agentsagiaiai-memoryaudio-recordingcomputer-visionhermeshermes-agentllmlocal-ailocal-firstmachine-learningmcpmultimodalopenclawprivacyrewindscreen-recordingspeech-to-textycombinator
fix(ci): disable telemetry inside the AppImage smoke containers
Louis Beaumontb6fbb8186116
diff --git a/.github/workflows/linux-appimage-smoke.yml b/.github/workflows/linux-appimage-smoke.ymlindex f229693e2..b8ab0a174 100644--- a/.github/workflows/linux-appimage-smoke.yml+++ b/.github/workflows/linux-appimage-smoke.yml@@ -252,7 +252,11 @@ jobs:mkdir -p /tmp/screenpipe-appimage-smokecp "apps/screenpipe-app-tauri/${APPIMAGE}" /tmp/screenpipe-appimage-smoke/screenpipe.AppImage+ # GITHUB_ACTIONS/CI do not cross the container boundary, so+ # telemetry_disabled_by_env() cannot see them. Without this the smoke+ # run reports as a real install and pollutes PostHog retention.docker run --rm \+ -e SCREENPIPE_DISABLE_TELEMETRY=1 \-v /tmp/screenpipe-appimage-smoke:/smoke \debian:trixie \bash -euxo pipefail -c '@@ -393,7 +397,10 @@ jobs:cp "apps/screenpipe-app-tauri/${APPIMAGE}" /tmp/screenpipe-appimage-arch/screenpipe.AppImagecp .github/scripts/linux/pipewire-context-smoke.c /tmp/screenpipe-appimage-arch/+ # See the Debian smoke step: the container does not inherit+ # GITHUB_ACTIONS/CI, so telemetry must be disabled explicitly.docker run --rm \+ -e SCREENPIPE_DISABLE_TELEMETRY=1 \-v /tmp/screenpipe-appimage-arch:/smoke \archlinux:latest \bash -euxo pipefail -c '