Add more better logging

[mvdwetering]

Summary by CodeRabbit

• New Features
  • Enhanced error logging capabilities to include debug messages and detailed exception information for improved troubleshooting.

[coderabbitai]

Walkthrough

The recent updates to the aiohuesyncbox package aim to improve logging within the library. These changes introduce logging features to facilitate error handling processes and provide detailed information during host resolution and request handling, enhancing the overall debugging experience for developers.

Changes

File Path	Change Summary
.../errors.py	Added logging functionality using the logging module for debug messages on errors.
.../huesyncbox.py	Enhanced logging by adding details to the resolve method and handling aiohttp.ClientError and asyncio.TimeoutError in the request method.

Poem

🐇🌟
In the realm of code, where logs align,
A rabbit weaves tales, errors defined.
Through leaps and bounds, in the code's moonlight,
Errors now traced, shining ever so bright.
Debug with glee, as logs unfold,
A sync saga told, in lines of gold. 🌙
🐇🌟

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 44b4da1 and 56db240.

Files selected for processing (1)

• aiohuesyncbox/errors.py (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• aiohuesyncbox/errors.py

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Consider using f-strings for better readability and performance in logging statements.

- logger.debug("raise_error, %s, %s, %s" % (code, message, cls))
+ logger.debug(f"raise_error, {code}, {message}, {cls}")

---

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	logger.debug("raise_error, %s, %s, %s" % (code, message, cls))
	logger.debug(f"raise_error, {code}, {message}, {cls}")