You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Retry arXiv scrape on suspicious zero-paper result, surface failures distinctly
Three consecutive weekday runs (7/22-7/24) reported 0 papers despite the listing page matching today's date, versus a historical baseline of 70-150/day. A live workflow_dispatch debug run confirmed the same GitHub Actions network gets the correct page moments later, so this is a transient CDN/origin blip around the scheduled run time, not a real quiet day or an IP block. Retries the listing fetch a few times on an unexpected 0, and if it's still 0, posts a distinct warning instead of the normal calm 'no relevant papers today' message so a real failure is never silently indistinguishable from a genuinely quiet day. Also adds a descriptive User-Agent per arXiv's robots policy.
console.log(` ⚠️ Listing page matched today's date but had 0 papers (attempt ${attempt}/${ZERO_IDS_RETRY_ATTEMPTS}) — retrying in ${ZERO_IDS_RETRY_DELAY_MS/1000}s in case of a transient CDN/origin blip...`);
text: "_arxiv.org/list/astro-ph/new matched today's date but returned 0 papers, even after retries. This is very unlikely to be a real zero-paper day — the scrape probably hit a transient arXiv/CDN issue. No papers were recorded as checked, so a manual re-run today (workflow_dispatch) should pick them up — tomorrow's run will only see tomorrow's listing, not today's._"}},
314
+
]);
315
+
return;
316
+
}
276
317
console.log(` ${fetched.length} papers found on arxiv.org/list/astro-ph/new.`);
277
318
278
319
// Skip anything already digested on a previous day (e.g. cross-listings)
0 commit comments