Skip to content

[Bug] Client exit on name resolve failure #351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
4 tasks done
snowie2000 opened this issue Mar 24, 2025 · 0 comments
Open
4 tasks done

[Bug] Client exit on name resolve failure #351

snowie2000 opened this issue Mar 24, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@snowie2000
Copy link
Contributor

snowie2000 commented Mar 24, 2025

Checklist

  • I have updated the version to the latest Release version
  • I've read the documentation in detail and still can't solve it
  • I have searched existing Issues | Discussions, but still can't solve it
  • I've tried a Google search and still can't figure it out

💻 Operating System

Debian12

🐛 Bug Description

The problem lies in this line:

let tcp_addr = domain.to_socket_addrs()?.next().unwrap();

When there is a network issue or DNS issue or something unexpected happens, the client simply exits with an error.

There should be at least a retry logic or even infinite retries with exponentially growing (with an upper limit) intervals to avoid report interruption.

🚦 Expected Behavior

No response

📷 Recurrence Steps

No response

📝 Additional Information

No response

@snowie2000 snowie2000 added the bug Something isn't working label Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant