feat: Adding more logs!

[amindadgar]

Adding more logs to memberactivities to find out the problem of #102

Summary by CodeRabbit

• Improvements
  • Enhanced progress visibility during member activity analysis with new logging statements.

[coderabbitai]

Walkthrough

The recent update focuses on enhancing the compute_member_activity function within the Discord Analyzer project by integrating comprehensive logging statements. These additions are designed to provide clear insights into the function's progress, thereby aiding in debugging and monitoring the analysis process.

Changes

File	Change Summary
discord_analyzer/analysis/compute_member_activity.py	Added logging statements at various points in the compute_member_activity function to provide information about the progress of the analysis.

Poem

In the depths of code, where data flows,
Logs now shine, like bright halos. 🌟
Each line whispers, "I'm on my way,"
To help debug and save the day!
The rabbits cheer, with joyful might,
For insights clear, and coding bright! 🐇

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ab1a50c and 4c2ae0c.

Files selected for processing (1)

• discord_analyzer/analysis/compute_member_activity.py (6 hunks)

Additional comments not posted (5)

discord_analyzer/analysis/compute_member_activity.py (5)

110-110: Good addition: Logging the start of member activities analysis.

This logging statement provides useful information about the start of the member activities analysis for the given guild ID.

---

153-153: Good addition: Logging the loading of past data.

This logging statement provides useful information about the process of loading past data.

---

178-178: Good addition: Logging the update of dictionaries.

This logging statement provides useful information about the completion of the dictionary update process.

---

185-185: Good addition: Logging the update of the date range.

This logging statement provides useful information about the process of updating the date range.

---

197-197: Good addition: Logging the update of joined members with past data.

This logging statement provides useful information about the process of updating joined members with past data.

[coderabbitai]

Redundant logging statement: Remove the duplicate log.

This logging statement is redundant as it repeats the message logged at line 153.

-    logging.info(f"{guild_msg} loading past data!")

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. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

logging.info(f"{guild_msg} loading past data!")

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4c2ae0c and baca457.

Files selected for processing (1)

• discord_analyzer/analysis/compute_member_activity.py (5 hunks)

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

• discord_analyzer/analysis/compute_member_activity.py