Ultimate-Multisite / Ultimate-Multisite/gratis-ai-feedback

Supervisor health dashboard stale: 2d0h (#3)

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-dispatch origin:worker priority:high review-followup status:available
Dominant language
PHP
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Premise

The dashboard at #3 last refreshed 2026-05-22T04:19:50Z2d0h ago (threshold: 2d0h). The stats-wrapper.sh scheduler is likely failing silently.

Why this matters

The supervisor health dashboard is the framework's primary single-glance health surface. When it stops refreshing, operators keep trusting green numbers that no longer reflect reality — every decision derived from "dashboard says green" becomes invalid.

Triage

  1. Inspect the stats scheduler status (macOS):

    launchctl list | grep -i aidevops-stats-wrapper
    tail -40 ~/.aidevops/logs/stats.log
    ls -la ~/Library/LaunchAgents/com.aidevops.aidevops-stats-wrapper.plist
    
  2. Run the refresh manually and capture the error:

    bash ~/.aidevops/agents/scripts/stats-wrapper.sh 2>&1 | tail -40
    
  3. Check the dashboard issue directly:

    gh api repos/Ultimate-Multisite/gratis-ai-feedback/issues/3 --jq '{updated_at, body_length: (.body|length)}'
    

Remediation

  • Missing plist: re-run setup.sh --non-interactive (or aidevops update) with PULSE_ENABLED=true so setup_stats_wrapper reinstalls com.aidevops.aidevops-stats-wrapper.plist.
  • set -euo pipefail fail: the post-t2418 wrapper emits HEALTH-DASHBOARD-FAIL exit=<N> on error. Grep stats.log on that prefix.
  • Body size / API error: inspect stats.log — look at gh HTTP errors and _update_health_issue_for_repo failures.

Acceptance

  • Root cause identified and documented on this issue.
  • gh issue view 3 --repo Ultimate-Multisite/gratis-ai-feedback shows an update within 24h of closing this alert.
  • last_refresh: marker is present in the dashboard body.

aidevops.sh v3.17.29 automated scan.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the macOS LaunchAgent status, ~/.aidevops/logs/stats.log, and ~/.aidevops/agents/scripts/stats-wrapper.sh; run the listed manual refresh command to capture the failure. Check setup.sh and dashboard issue #3 after identifying the root cause. Done means the cause is documented, issue #3 updates within 24 hours, and its body contains a last_refresh: marker.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, macos, shell
Domain
cli, devops, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.