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

Fix npe of audit log get operator #5153

Merged

Conversation

BlackBear2003
Copy link
Contributor

@BlackBear2003 BlackBear2003 commented Jun 9, 2024

What's the purpose of this PR

To fix existing NPE bug in audit logging

when there is no active span exists on request thread context, trying to get operator will cause NPE by continuously get().

  • causing NPE codes
      if (tracer != null) {
        return ((ApolloAuditTracer) tracer).scopeManager().activeSpan().operator();
      }
  • prof by unit test

image

In some case this bug will appear:

Set audit.log.enabled=false in Portal and audit.log.enabled=true in AdminService.

In this case, no activeSpan would be passed to AdminService, meanwhile AdminService would get operator through active span. And then cause NPE.

Brief changelog

  1. Fix this continuously get()
  2. Reduce inelegant ways of exposing interfaces to the outside
  3. Add unit test for ApolloAuditOperatorDefaultSupplier

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Read the Contributing Guide before making this pull request.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit tests to verify the code.
  • Run mvn clean test to make sure this pull request doesn't break anything.
  • Update the CHANGES log.

Summary by CodeRabbit

  • Bug Fixes

    • Improved the retrieval of the active span's operator in audit logs, defaulting to "anonymous" if no active span exists.
  • Tests

    • Added new test cases to ensure correct behavior when an active span is present or absent during audit operations.

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Jun 9, 2024
Copy link
Contributor

coderabbitai bot commented Jun 9, 2024

Walkthrough

The changes primarily involve modifying access levels and enhancing functionality related to auditing in the Apollo framework. The scopeManager method in ApolloAuditTracer is now protected instead of public. Enhancements in ApolloAuditOperatorDefaultSupplier enable it to fetch the operator from the active audit span. Corresponding tests have been added to validate these behaviors.

Changes

File Path Summary of Changes
.../ApolloAuditTracer.java Changed scopeManager method's access modifier from public to protected.
.../ApolloAuditOperatorDefaultSupplier.java Added import for ApolloAuditSpan and modified getOperator method to fetch operator from the active span or return "anonymous".
.../ApolloAuditOperatorSupplierTest.java Added test methods for scenarios with and without an active span. Included necessary imports for testing.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant ApolloAuditOperatorDefaultSupplier
    participant ApolloAuditSpan
    participant ApolloAuditTracer

    Client->>ApolloAuditOperatorDefaultSupplier: getOperator()
    ApolloAuditOperatorDefaultSupplier->>ApolloAuditTracer: scopeManager()
    ApolloAuditTracer-->>ApolloAuditOperatorDefaultSupplier: ApolloAuditScopeManager
    ApolloAuditOperatorDefaultSupplier->>ApolloAuditSpan: getActiveSpan()
    alt Active Span Exists
        ApolloAuditSpan-->>ApolloAuditOperatorDefaultSupplier: operator
    else No Active Span
        ApolloAuditOperatorDefaultSupplier-->>Client: "anonymous"
    end
Loading

Poem

In the code where audits bloom,
Changes sweep away the gloom.
Protected methods, spans in flight,
Operators now in clear sight.
Tests ensure the path is true,
Apollo's audit shines anew. 🌟


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>.
    • 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.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1e18d54 and b300cbf.

Files selected for processing (3)
  • apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/context/ApolloAuditTracer.java (1 hunks)
  • apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/spi/defaultimpl/ApolloAuditOperatorDefaultSupplier.java (2 hunks)
  • apollo-audit/apollo-audit-impl/src/test/java/com/ctrip/framework/apollo/audit/spi/ApolloAuditOperatorSupplierTest.java (1 hunks)
Additional comments not posted (3)
apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/spi/defaultimpl/ApolloAuditOperatorDefaultSupplier.java (1)

20-20: Approved the addition of necessary imports for handling the active span.

apollo-audit/apollo-audit-impl/src/test/java/com/ctrip/framework/apollo/audit/spi/ApolloAuditOperatorSupplierTest.java (1)

1-74: Approved the comprehensive tests for both scenarios of active span existence. The imports are correctly added to support the testing framework.

apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/context/ApolloAuditTracer.java (1)

46-46: Approved the change in access modifier for scopeManager() to protected. Ensure this change does not affect any existing calls from outside the package that relied on this being public.

Verification successful

The verification confirms that the scopeManager() method is not called from outside its package, and there are no subclasses of ApolloAuditTracer within the package that might indirectly access it. The method is only used within the ApolloAuditTracer class itself.

  • : The change in access modifier for scopeManager() to protected does not affect any existing functionality outside its package.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify if the `scopeManager()` method is called from outside its package.

# Test: Search for the method usage outside its package. Expect: No occurrences outside its package.
rg --type java --glob '!apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/context/*' 'scopeManager()'

Length of output: 131



Script:

#!/bin/bash
# Description: Verify if the `scopeManager()` method is used indirectly or through subclasses within the package.

# Test 1: Search for subclasses of ApolloAuditTracer within the package.
rg --type java --pattern 'class .* extends ApolloAuditTracer' apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/context/

# Test 2: Search for any indirect access to `scopeManager()` within the package.
rg --type java --pattern 'scopeManager()' apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/context/

Length of output: 1105



Script:

#!/bin/bash
# Description: Verify if the `scopeManager()` method is used indirectly or through subclasses within the package.

# Test 1: Search for subclasses of ApolloAuditTracer within the package.
rg 'class .* extends ApolloAuditTracer' apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/context/

# Test 2: Search for any indirect access to `scopeManager()` within the package.
rg 'scopeManager()' apollo-audit/apollo-audit-impl/src/main/java/com/ctrip/framework/apollo/audit/context/

Length of output: 1038

Copy link
Member

@nobodyiam nobodyiam left a comment

Choose a reason for hiding this comment

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

LGTM

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jun 10, 2024
@nobodyiam nobodyiam merged commit 6218cdd into apolloconfig:master Jun 10, 2024
7 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jun 10, 2024
@BlackBear2003 BlackBear2003 deleted the fix-NPE-of-audit-log-getOperator branch June 10, 2024 07:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm This PR has been approved by a maintainer size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants