-
Notifications
You must be signed in to change notification settings - Fork 53
Tracker Checker: handle HTTP Tracker timeouts #679
Copy link
Copy link
Closed
Labels
- Admin -Enjoyable to Install and Setup our SoftwareEnjoyable to Install and Setup our Software- Developer -Torrust Improvement ExperienceTorrust Improvement ExperienceCode Cleanup / RefactoringTidying and Making NeatTidying and Making NeatEasyGood for NewcomersGood for NewcomersEnhancement / Feature RequestSomething NewSomething NewTestingChecking TorrustChecking Torrustgood first issueGood for newcomersGood for newcomers
Milestone
Metadata
Metadata
Assignees
Labels
- Admin -Enjoyable to Install and Setup our SoftwareEnjoyable to Install and Setup our Software- Developer -Torrust Improvement ExperienceTorrust Improvement ExperienceCode Cleanup / RefactoringTidying and Making NeatTidying and Making NeatEasyGood for NewcomersGood for NewcomersEnhancement / Feature RequestSomething NewSomething NewTestingChecking TorrustChecking Torrustgood first issueGood for newcomersGood for newcomers
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Done
Parent issue: #677
You can run a Tracker Checker with:
The HTTP Tracker client does not have any timeout so it will wait forever.
We have to add a
timeoutto the HTTP client requests:You can add a timeout to all
reqwest.getlike this in the Health Check:You can force the error by adding a
sleepin the handler:This issue should be implemented after refactoring the HTTP Tracker client to return errors instead of panicking.