-
Notifications
You must be signed in to change notification settings - Fork 52
Tracker Checker: Improve errors. More concrete errors #676
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 NewLow PriorityNot our Focus NowNot our Focus NowTestingChecking 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 NewLow PriorityNot our Focus NowNot our Focus NowTestingChecking TorrustChecking Torrustgood first issueGood for newcomersGood for newcomers
Type
Projects
Status
Done
Parent issue: #669
Relates to:
ConnectionRefused#683Currently, you can run the Tracker Checker with this input:
When something is wrong you only get three types of errors or the application panics.
For example:
Output:
Errors are defined with this enum:
But depending on the service there could be different reasons. For example:
For the Health Check:
For the UDP tracker:
We should introduce a second level of types for errors. For example:
This issue should be implemented after implementing other issues related to timeout errors. Because those issues might introduce new errors.