Skip to content

fix(rss): retry curl on DNS failures when fetching news feeds#182

Merged
exequtic merged 1 commit into
exequtic:mainfrom
AndyHazz:fix/curl-retry-dns-failures
Feb 15, 2026
Merged

fix(rss): retry curl on DNS failures when fetching news feeds#182
exequtic merged 1 commit into
exequtic:mainfrom
AndyHazz:fix/curl-retry-dns-failures

Conversation

@AndyHazz
Copy link
Copy Markdown
Contributor

Summary

  • curl's --retry does not retry on DNS resolution failures (exit code 6) by default — only on timeouts and HTTP errors. This causes intermittent "Cannot fetch news" errors on systems without a local DNS cache when the resolver briefly fails.
  • Added --retry-all-errors to the RSS feed curl call so it retries on all transient errors including DNS failures
  • Bumped retries from 2 to 3 and added --retry-delay 1 for a 1-second pause between attempts

Context

On systems using NetworkManager without systemd-resolved or dnsmasq, there is no local DNS cache. Brief DNS resolver hiccups cause the RSS fetch to fail immediately with no retry, producing the "Cannot fetch news" error in the widget. With --retry-all-errors, curl will retry these transient DNS failures before giving up.

🤖 Generated with Claude Code

curl's --retry does not retry on DNS resolution failures (exit code 6)
by default, only on timeouts and HTTP errors. This causes intermittent
"Cannot fetch news" errors when the local DNS resolver briefly fails.

Add --retry-all-errors to retry on all transient errors including DNS,
bump retries from 2 to 3, and add --retry-delay 1 for a 1-second pause
between attempts.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@exequtic exequtic merged commit 9b99fd4 into exequtic:main Feb 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants