Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

logging is consistent with the new group-specific preference management #4080

Merged
merged 1 commit into from
Dec 14, 2024

Conversation

Baalmart
Copy link
Contributor

@Baalmart Baalmart commented Dec 14, 2024

Description

logging is consistent with the new group-specific preference management

Changes Made

  • Added validation for group membership using group_roles, similar to the preference update job.
  • Used constants.DEFAULT_GROUP to filter preferences.
  • Filtered users to only include those in the default group.
  • Updated the query for fetching preferences to include both user_id and group_id.
  • Modified the logging message to be more specific about the default group.
  • Added error handling and logging similar to the preference update job.
  • Added a module export for potential testing or manual invocation.

Testing

  • Tested locally
  • Tested against staging environment
  • Relevant tests passed: [List test names]

Affected Services

  • Which services were modified:
    • Auth Service

API Documentation Updated?

  • Yes, API documentation was updated
  • No, API documentation does not need updating

Additional Notes

The refactored job now:

  • Checks user group membership
  • Filters preferences for the default group
  • Tracks the number of users without selected sites in the default group
  • Provides more precise logging about user preferences

This approach aligns with the recent changes in the preference update job and ensures that the logging is consistent with the new group-specific preference management.

Copy link
Contributor

coderabbitai bot commented Dec 14, 2024

📝 Walkthrough

Walkthrough

The pull request modifies the logUserPreferences function in the authentication service's preferences log job. The primary enhancement focuses on filtering users based on their group roles, specifically targeting users in the default group. The changes refine the user preference logging mechanism to provide more precise insights by concentrating on a specific user group and improving the logging granularity.

Changes

File Change Summary
src/auth-service/bin/jobs/preferences-log-job.js - Added group role filtering for users
- Updated user preferences query to match default group
- Modified logging statements to reflect default group focus
- Exported logUserPreferences function

Suggested Reviewers

  • OchiengPaul442
  • Codebmk

Possibly Related PRs

Poem

🔍 Filtering users with surgical grace,
Default group takes center stage,
Preferences logged with newfound might,
Code refactored, insights burning bright!
A digital dance of data's delight 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. This feature will be included in our Pro Plan when released.


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
🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Copy link

codecov bot commented Dec 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 11.81%. Comparing base (331742e) to head (b907f64).
Report is 8 commits behind head on staging.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff            @@
##           staging    #4080   +/-   ##
========================================
  Coverage    11.81%   11.81%           
========================================
  Files          115      115           
  Lines        15482    15482           
  Branches       319      319           
========================================
  Hits          1829     1829           
  Misses       13653    13653           

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (4)
src/auth-service/bin/jobs/preferences-log-job.js (4)

17-21: LGTM! Consider adding JSDoc type annotations.

The variable declarations and initialization look good. The use of mongoose.Types.ObjectId for the group ID is appropriate.

Consider adding JSDoc type annotations for better code documentation:

+/** @type {number} */
 let totalCountWithoutSelectedSites = 0;
+/** @type {number} */
 let totalUsersProcessed = 0;
+/** @type {mongoose.Types.ObjectId} */
 const defaultGroupId = mongoose.Types.ObjectId(constants.DEFAULT_GROUP);

45-51: Add error handling for preference fetching.

While the preference fetching logic is well-implemented, it could benefit from better error handling.

-      const preferences = await PreferenceModel("airqo")
-        .find({
-          user_id: { $in: userIds },
-          group_id: defaultGroupId,
-        })
-        .select("_id user_id selected_sites")
-        .lean();
+      let preferences = [];
+      try {
+        preferences = await PreferenceModel("airqo")
+          .find({
+            user_id: { $in: userIds },
+            group_id: defaultGroupId,
+          })
+          .select("_id user_id selected_sites")
+          .lean();
+      } catch (error) {
+        logger.error(`Failed to fetch preferences: ${stringify(error)}`);
+        // Continue with empty preferences rather than breaking the job
+      }

60-68: Optimize the filtering of users without selected sites.

The current implementation is correct but can be made more efficient by reducing iterations.

-      const usersWithoutSelectedSites = validUsers.filter((user) => {
-        const preference = preferencesMap.get(user._id.toString());
-        return !preference || isEmpty(preference.selected_sites);
-      });
-
-      // Aggregate results
-      totalCountWithoutSelectedSites += usersWithoutSelectedSites.length;
-      totalUsersProcessed += validUsers.length;
+      // Combine filtering and counting in one pass
+      let batchUsersWithoutSites = 0;
+      for (const user of validUsers) {
+        const preference = preferencesMap.get(user._id.toString());
+        if (!preference || isEmpty(preference.selected_sites)) {
+          batchUsersWithoutSites++;
+        }
+      }
+      totalCountWithoutSelectedSites += batchUsersWithoutSites;
+      totalUsersProcessed += validUsers.length;

74-86: Enhance logging with structured data.

While the current logging is informative, structured logging would make it easier to parse and analyze the data.

-      logger.info(
-        `💔💔 Total count of users without Customised Locations in the default group: ${totalCountWithoutSelectedSites}, which is ${percentageWithoutSelectedSites}% of processed users.`
-      );
+      logger.info({
+        message: "Completed processing users without Customised Locations",
+        totalUsersWithoutLocations: totalCountWithoutSelectedSites,
+        totalUsersProcessed,
+        percentageWithoutLocations: parseFloat(percentageWithoutSelectedSites),
+        defaultGroupId: defaultGroupId.toString()
+      });
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 45e099b and b907f64.

📒 Files selected for processing (1)
  • src/auth-service/bin/jobs/preferences-log-job.js (4 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
src/auth-service/bin/jobs/preferences-log-job.js

[error] 39-42: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

🔇 Additional comments (1)
src/auth-service/bin/jobs/preferences-log-job.js (1)

98-99: LGTM! Export enables testing as intended.

The module export is correctly implemented and aligns with the PR objective of facilitating testing and manual invocation.

Comment on lines +24 to +43
// Fetch users with their group_roles
const users = await UserModel("airqo")
.find()
.limit(batchSize)
.skip(skip)
.select("_id email")
.select("_id email group_roles")
.lean();

if (users.length === 0) {
break;
}

// Fetch existing preferences for users in batch
const userIds = users.map((user) => user._id);
// Filter users who are members of the default group
const validUsers = users.filter(
(user) =>
user.group_roles &&
user.group_roles.some(
(role) => role.group.toString() === defaultGroupId.toString()
)
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Optimize group role filtering and add safety checks.

The user fetching logic is well-structured, but there are a few improvements we can make:

  1. Use optional chaining as suggested by static analysis:
-          user.group_roles &&
-          user.group_roles.some(
+          user.group_roles?.some(
  1. Add index hint for better query performance:
 const users = await UserModel("airqo")
   .find()
+  .hint({ group_roles: 1 })
   .limit(batchSize)
   .skip(skip)
   .select("_id email group_roles")
   .lean();
  1. Consider caching the defaultGroupId.toString() result:
+      const defaultGroupIdString = defaultGroupId.toString();
       const validUsers = users.filter(
         (user) =>
           user.group_roles?.some(
-            (role) => role.group.toString() === defaultGroupId.toString()
+            (role) => role.group.toString() === defaultGroupIdString
           )
       );

Committable suggestion skipped: line range outside the PR's diff.

🧰 Tools
🪛 Biome (1.9.4)

[error] 39-42: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

Copy link
Contributor

Auth-service changes in this PR available for preview here

@Baalmart Baalmart merged commit 2c21940 into staging Dec 14, 2024
52 checks passed
@Baalmart Baalmart deleted the hf-logging-preferences branch December 14, 2024 10:24
@Baalmart Baalmart mentioned this pull request Dec 14, 2024
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant