Tracker Checker: Improve errors. More concrete errors #676
Labels
- Admin -
Enjoyable to Install and Setup our Software
- Developer -
Torrust Improvement Experience
Code Cleanup / Refactoring
Tidying and Making Neat
Easy
Good for Newcomers
Enhancement / Feature Request
Something New
good first issue
Good for newcomers
Low Priority
Not our Focus Now
Testing
Checking Torrust
Milestone
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.
The text was updated successfully, but these errors were encountered: