From 2c96eee5d6b1a16fc687fc06d9ba001e743f5450 Mon Sep 17 00:00:00 2001 From: Tim Morgan Date: Sun, 1 Nov 2026 22:38:11 -0800 Subject: [PATCH 1/3] Poll for new NASR cycles weekly NASR cycles take effect every 28 days and the FAA posts each about 29 days ahead, so a daily poll found nothing new on 27 of every 28 runs. A Monday poll still finds a new cycle within a week of posting, and the overdue alert (missing within 14 days of the effective date) still has at least one poll in its window. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/nasr-cycle-watch.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/nasr-cycle-watch.yml b/.github/workflows/nasr-cycle-watch.yml index 0ea5672..a537e44 100644 --- a/.github/workflows/nasr-cycle-watch.yml +++ b/.github/workflows/nasr-cycle-watch.yml @@ -6,7 +6,9 @@ name: NASR Cycle Watch on: schedule: - - cron: "0 16 * * *" + # Mondays. The FAA posts a cycle about 29 days ahead, so a weekly poll finds it within a week + # and still has two weeks of margin before the overdue alert. + - cron: "0 16 * * 1" workflow_dispatch: inputs: cycle: From 982b2e710851e630f3f37543dd3d67cb4b65361f Mon Sep 17 00:00:00 2001 From: Tim Morgan Date: Sun, 1 Nov 2026 22:40:32 -0800 Subject: [PATCH 2/3] Describe the polling cadence in remaining comments Comments still described the old daily polling ("every day", "daily", "quiet day"). They now say "poll", which holds for the new schedule. Report artifacts keep 90 days, longer than any gap between runs, so retention is unchanged. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/nasr-cycle-watch.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/nasr-cycle-watch.yml b/.github/workflows/nasr-cycle-watch.yml index a537e44..53de51e 100644 --- a/.github/workflows/nasr-cycle-watch.yml +++ b/.github/workflows/nasr-cycle-watch.yml @@ -101,7 +101,7 @@ jobs: days_out=$(( ( $(date -u -d "$CYCLE" +%s) - $(date -u +%s) ) / 86400 )) # Publication runs ~29 days ahead; still missing two weeks out means the FAA slipped or - # the URLs moved, either of which otherwise looks like an ordinary quiet day. + # the URLs moved, either of which otherwise looks like an ordinary quiet poll. if [ "$available" != "true" ] && [ "$days_out" -le 14 ]; then overdue=true else @@ -317,7 +317,7 @@ jobs: - name: Upload the report # Uploaded before anything reads it, and on failure too: this artifact is also the record - # that the cycle was checked, so a broken cycle is reported once rather than every day. + # that the cycle was checked, so a broken cycle is reported once rather than on every poll. if: always() uses: actions/upload-artifact@v7.0.2 with: From d37fc501a0e9db65e2503e9e4534de23fd75582b Mon Sep 17 00:00:00 2001 From: Tim Morgan Date: Sun, 1 Nov 2026 22:43:41 -0800 Subject: [PATCH 3/3] Tolerate a missing Last-Modified header on an unpublished cycle An unpublished cycle answers the range GET with 404 and no Last-Modified header. grep then exits 1, and under set -eo pipefail that aborted the availability step before available=false or the overdue check could be set. Guarding the grep, as SwiftCIFP does, leaves published empty and lets the step fall through. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/nasr-cycle-watch.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/nasr-cycle-watch.yml b/.github/workflows/nasr-cycle-watch.yml index 53de51e..eef77a7 100644 --- a/.github/workflows/nasr-cycle-watch.yml +++ b/.github/workflows/nasr-cycle-watch.yml @@ -97,7 +97,7 @@ jobs: available=false fi - published=$(grep -i '^last-modified:' txt.headers | tail -n 1 | cut -d' ' -f2- | tr -d '\r') + published=$({ grep -i '^last-modified:' txt.headers || true; } | tail -n 1 | cut -d' ' -f2- | tr -d '\r') days_out=$(( ( $(date -u -d "$CYCLE" +%s) - $(date -u +%s) ) / 86400 )) # Publication runs ~29 days ahead; still missing two weeks out means the FAA slipped or