fix: readd lost custom errors

[Nidhi091999]

Issue: #168

Summary by Sourcery

Add InputUriError and IPDistanceCalculationError exceptions, and add a TesUriError exception.

New Features:

• Added InputUriError for signaling invalid input URIs.
• Added IPDistanceCalculationError for when IP distance calculation fails.
• Added TesUriError for when a TES URI cannot be parsed.

Summary by Sourcery

Reintroduce and define custom error classes for specific error scenarios in the exceptions module

New Features:

• Added custom error classes for TES URI parsing
• Added custom error classes for input URI parsing
• Added custom error class for IP distance calculation failures

Bug Fixes:

• Restored previously lost custom error exceptions

[sourcery-ai]

Reviewer's Guide

This pull request re-introduces three custom exception classes (InputUriError, IPDistanceCalculationError, TesUriError) by defining them in pro_tes/exceptions.py and registering them in the exceptions dictionary with associated messages and HTTP status codes.

Class diagram for new exception types

classDiagram
    ValueError <|-- InputUriError
    note for InputUriError "Added in this PR"
    ValueError <|-- IPDistanceCalculationError
    note for IPDistanceCalculationError "Added in this PR"
    ValueError <|-- TesUriError
    note for TesUriError "Added in this PR"

Loading

File-Level Changes

Change	Details	Files
Added custom exception classes and registered them.	Defined TesUriError, InputUriError, and IPDistanceCalculationError inheriting from ValueError. Added entries for the new exceptions in the exceptions dictionary, mapping them to error messages and HTTP status codes (400 or 500).	pro_tes/exceptions.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Nidhi091999 - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please fill out the PR description with details about the motivation for these new exceptions and reference any related issues.
• The exceptions dictionary entries should maintain consistency - TesUriError and IPDistanceCalculationError are missing HTTP status codes while other entries have them.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue: Missing error code for TesUriError and IPDistanceCalculationError exceptions

Other exceptions in the dictionary include both 'message' and 'code' fields. Consider adding appropriate error codes to maintain consistency in error handling.

[uniqueg]

Let's get to this after the repo is fixed again (broken tests) and after #184 is merged :)

[sourcery-ai]

Hey @Nidhi091999 - I've reviewed your changes - here's some feedback:

• Consider inheriting the new custom exceptions from a shared base exception class specific to this application for better error categorization.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}