Alexander Whitestone
097ff176c8
Some checks failed
Architecture Lint / Linter Tests (pull_request) Successful in 6s
PR Checklist / pr-checklist (pull_request) Failing after 1m10s
Smoke Test / smoke (pull_request) Failing after 6s
Validate Config / YAML Lint (pull_request) Failing after 4s
Validate Config / JSON Validate (pull_request) Successful in 4s
Validate Config / Python Syntax & Import Check (pull_request) Failing after 12s
Validate Config / Shell Script Lint (pull_request) Failing after 13s
Validate Config / Cron Syntax Check (pull_request) Successful in 3s
Validate Config / Deploy Script Dry Run (pull_request) Successful in 3s
Validate Config / Playbook Schema Validation (pull_request) Successful in 6s
Architecture Lint / Lint Repository (pull_request) Has been cancelled
Validate Config / Python Test Suite (pull_request) Has been cancelled
Problem: Once a pipeline completes (Monday), its 'completed' status persists forever. Tuesday's run sees it as 'completed' and skips it. Fix: Added reset_completed_pipelines() that: - Tracks pipeline_reset_date in state - On new day, resets 'completed' and 'failed' pipelines to 'not_started' - Preserves 'running' pipelines (don't kill active work) - Called at start of every run_scheduler() invocation Also added pipeline_reset_date to default state dict.