Fix watchdog crashes on transient network errors

[Copilot]

doduda listen terminates on any network error (timeouts, DNS failures, HTTP errors) because GetLatestLauncherVersion uses log.Fatal(). Since the API structure is stable (restarting works), the watchdog should survive transient failures and retry.

Changes

• update.go: Refactored GetLatestLauncherVersion to return errors instead of calling log.Fatal()

  • Changed signature: func() string → func() (string, error)
  • Added safe type assertions with error checks to prevent panics on API structure changes
  • Added HTTP status code validation
  • Properly closes response body with defer

• watchdog.go: Propagate errors up to watchdogTick which logs and continues

  if err != nil {
      log.Error(err)  // Logs but doesn't terminate
  }

• main.go: Handle errors in versionCommand

Behavior

Before: Network error → process exits → manual restart required

After: Network error → logged → continues → retries on next interval (default 5min)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• cytrus.cdn.ankama.com
  • Triggering command: curl -s REDACTED (dns block)
  • Triggering command: curl -v REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Watchdog dies</issue_title>
<issue_description>doduda listen dies with unknown cause on the dofusdude server since one of the newest major updates to Dofus.

There is a hack running to ensure updates are reaching the servers but this problem should be taken care of soon.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Watchdog dies #46

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[stelzo]

main.go L296 still is a log.Fatal, so how does this keep the server always running? @copilot

[Copilot]

main.go L296 still is a log.Fatal, so how does this keep the server always running? @copilot

Line 296 is in versionCommand which handles the doduda version command - a one-shot command that prints the version and exits. It's appropriate to fail-fast there.

The watchdog (doduda listen) uses watchdogCommand (lines 355-428) which calls watchdogTick in a ticker loop. The key fix is in watchdogTick (watchdog.go:107-112) which now logs errors with log.Error(err) and continues running instead of crashing, allowing the watchdog to survive transient failures and retry on the next interval.