Improve cache update reliability and monitoring

[neubig]

This PR improves the reliability of the cache update system and adds better monitoring capabilities.

Changes

1. Improved Error Handling and Retries

• Added retry mechanism with configurable attempts
• Added rate limit detection and handling
• Better error logging with detailed information
• Added User-Agent header to prevent GitHub API issues

2. Better Monitoring and Logging

• Created a new status endpoint (/api/status.js)
• Added detailed logging in the cron job
• Created a monitoring script (monitor-cache.ts)
• Status file tracks last successful update and errors

3. Improved Cache Building Process

• Modified the cron endpoint to handle errors better
• Added status tracking during cache updates
• Created a safer cache building script (build:cache:safe)

4. Added Health Checks

• New monitoring script to check cache health
• Checks for cache staleness (>12 hours old)
• Verifies cache content validity
• Reports detailed status information

Testing

To test these changes:

1. Run npm run monitor:cache to check cache health
2. Visit /api/status endpoint to view cache status
3. Try npm run build:cache:safe to test the safer cache building process

Notes

Make sure the following environment variables are set in Vercel:

• GITHUB_TOKEN
• CRON_SECRET

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
openhands-agent-monitor	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 18, 2024 7:14pm