fleet-nightly: read traffic and accounts from dev2, skip dead sources - #17
Merged
Merged
Conversation
Every run since 2026-09-25 died on 'sql on ywcizjsgrcmhgyplldac -> 404 Resource has been removed': crawlproof's Supabase cloud project was deleted when it moved to dev2, and so was every other property's that night. - traffic: tracker_event_daily_stats from crawlproof's Postgres on dev2 (CRAWLPROOF_DB_URL, vault fleet-nightly--prod), through Bun's built-in client in a session set read-only and checked before the query runs - accounts: auth.users on each property's self-hosted stack (URLs from the dev2 fleet kit's ~/.local/state/dev2-fleet/<site>.json, plus crawlproof's own DB), and any project still on Supabase cloud - every source may fail alone: a dead database is skipped and named under 'Sources skipped', and a property that had accounts last time and has no source now is named too; only a report with no source at all fails Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fleet-nightly has failed every night since 2026-09-25 with
sql on ywcizjsgrcmhgyplldac -> 404: Resource has been removed. crawlproof moved to dev2 and its Supabase cloud project was deleted. By 09-26 every other property's cloud project was gone as well, so repointing traffic alone would still have left signups and logins empty.Sources now
tracker_event_daily_statsin crawlproof's self-hosted Postgres (db.crawlproof.com),CRAWLPROOF_DB_URLin vaultfleet-nightly--prod. The tracker site list still comes from crawlproof's API.auth.userson each property's dev2 Supabase stack (sb_database_urlfrom the fleet kit's~/.local/state/dev2-fleet/<site>.json), crawlproof's own DB, and any project still on Supabase cloud (the management API path is kept).bun -eprocess runs every query. Each session is set totransaction read onlyand checked withshow transaction_read_onlybefore its query runs.Failures: each source may fail on its own. A dead DB or API is skipped and listed under "Sources skipped" in the email. A property that had accounts in the last snapshot but has no source now is named too (tonight: vu1nz.com, whose cloud project was empty and deleted). If traffic is down, the subject says
traffic unavailableinstead of reporting 0 views. Only a run with no source at all mails a FAILED notice.Proof (dry runs against the live sources)
Fleet nightly, Mon Sep 28: 4,953 views (-25%), 138 signups, 109 logins, 45 tracked, 21 with accounts, 1.9 s underenv -i(secrets from the vault)traffic unavailable, 77 signups, 35 logins,traffic skipped (… password authentication failed)andugig.net (Failed to connect)named🤖 Generated with Claude Code