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

chore: sonar ignore directories with their own go.mods #20509

Merged
merged 5 commits into from
May 31, 2024

Conversation

tac0turtle
Copy link
Member

@tac0turtle tac0turtle commented May 31, 2024

Description

ignore sonar coverage when a go.mod is created in the main sonar cloud config


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Chores
    • Updated configuration files to improve code quality checks and test coverage exclusions.

@tac0turtle tac0turtle marked this pull request as ready for review May 31, 2024 15:18
@tac0turtle tac0turtle requested a review from a team as a code owner May 31, 2024 15:18
Copy link
Contributor

coderabbitai bot commented May 31, 2024

Walkthrough

The recent updates primarily focus on configuration adjustments for code quality and coverage tools. The .golangci.yml file modifications include removing certain settings and reorganizing configurations, while the sonar-project.properties file sees an expansion in the list of directories and files excluded from coverage analysis. These changes streamline the configuration and ensure more targeted code quality checks.

Changes

Files Change Summary
.golangci.yml Removal of sort-results and exclude-dir settings, reorganization of build-tags, adjustment in linters, addition of exclude-dirs and exclude-files under issues.
sonar-project.properties Added exclusions for various directories and files to sonar.coverage.exclusions.

Sequence Diagram(s) (Beta)

No sequence diagrams are necessary for these changes as they are configuration file updates and do not alter the control flow or introduce new features.


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.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2e966a8 and 0759d9e.

Files selected for processing (2)
  • .golangci.yml (3 hunks)
  • sonar-project.properties (1 hunks)
Additional comments not posted (2)
.golangci.yml (2)

5-5: Ensure the build tags are correctly used across the project.

Verification successful

The build tags e2e, ledger, and test_ledger_mock are used correctly across the project.

  • Instances of build tags are found in various files, including test files and source files.
  • The usage of these tags is consistent and correctly formatted.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the build tags are used correctly in the project.

# Test: Search for the usage of build tags.
rg --type go $'// +build e2e|ledger|test_ledger_mock'

Length of output: 11304


38-47: Review the necessity of each exclusion to ensure they are justified.

Verification successful

The exclusions in the .golangci.yml file appear to be justified based on the following observations:

  • Test Files: Many files in the excluded directories are test files, which are typically excluded from linting to focus on the main codebase.
  • Generated Files: Files with extensions .pb.go, .pb.gw.go, and .pulsar.go are generated files, which are often excluded from linting because they are auto-generated and not manually edited.
  • Internal Implementation Details: Files in the crypto/keys/secp256k1/internal directory are internal implementation details, which are usually excluded to avoid linting internal dependencies that are not part of the public API.

Specific excluded files:

  • server/grpc/gogoreflection/fix_registration.go and fix_registration.go are present and likely serve a specific purpose that justifies their exclusion.
  • types/coin_regex.go is also present and may contain specific logic that warrants exclusion from linting.

Based on this analysis, the exclusions in the .golangci.yml file are justified.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the necessity of each exclusion in the `.golangci.yml`.

# Test: List files in the excluded directories and check for any Go files.
fd --type f --extension go --exec echo {} \; | grep -E 'testutil/testdata|crypto/keys/secp256k1/internal|types'

Length of output: 17085



Script:

#!/bin/bash
# Description: Verify the necessity of each exclusion in the `.golangci.yml`.

# Check if the excluded files are test files, generated files, or internal implementation details.

# Check for test files
grep -E 'test' <<< "$(fd --type f --extension go --exec echo {} \; | grep -E 'testutil/testdata|crypto/keys/secp256k1/internal|types')"

# Check for generated files
grep -E 'pb\.go|pb\.gw\.go|pulsar\.go' <<< "$(fd --type f --extension go --exec echo {} \; | grep -E 'testutil/testdata|crypto/keys/secp256k1/internal|types')"

# Check for internal implementation details
grep -E 'internal' <<< "$(fd --type f --extension go --exec echo {} \; | grep -E 'testutil/testdata|crypto/keys/secp256k1/internal|types')"

# Check for specific excluded files
fd --type f --extension go --exec echo {} \; | grep -E 'server/grpc/gogoreflection/fix_registration.go|fix_registration.go|types/coin_regex.go'

Length of output: 10501

@@ -6,7 +6,7 @@ sonar.project.monorepo.enabled=true

sonar.sources=.
sonar.exclusions=**/*_test.go,**/*.pb.go,**/*.pulsar.go,**/*.pb.gw.go
sonar.coverage.exclusions=**/*_test.go,**/testutil/**,**/*.pb.go,**/*.pb.gw.go,**/*.pulsar.go,test_helpers.go,docs/**
sonar.coverage.exclusions=**/*_test.go,**/testutil/**,**/*.pb.go,**/*.pb.gw.go,**/*.pulsar.go,test_helpers.go,docs/**,server/v2/**,store/v2/**,x/tx/**,tools/**,cmd/**,app/**,simapp/**,testutil/**,test_helpers.go,tests/**,test_helpers.go,docs/**,server/v2/**,store/**,x/tx/**,tools/**,simapp/**,tests/**,orm/**,client/v2/**,runtime/v2/**,core/**,store/**,x/evidence,x/feegrant,x/authz,x/auth,x/bank,api,x/gov
Copy link
Contributor

@coderabbitai coderabbitai bot May 31, 2024

Choose a reason for hiding this comment

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

Tip

Codebase Verification

The exclusions list in sonar-project.properties contains several duplicate entries that need to be removed:

  • **/*.pb.go
  • **/*.pb.gw.go
  • **/*.pulsar.go
  • test_helpers.go
  • docs/**
  • server/v2/**
  • x/tx/**
  • tools/**
  • simapp/**
  • tests/**
  • store/**
  • /testutil/

Please remove these duplicates to clean up the exclusions list.

Analysis chain

Ensure no duplicates in exclusions list.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Check for duplicate entries in the exclusions list.

# Test: Print duplicate entries if any.
awk -F',' '{for(i=1;i<=NF;i++) if(++dup[$i]>1) print $i}' sonar-project.properties

Length of output: 244

Copy link
Member

Choose a reason for hiding this comment

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

bot is right

Copy link
Contributor

Choose a reason for hiding this comment

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

@julienrbrt, thank you for confirming! If there's anything else you need help with or any other changes you'd like to review, feel free to let me know. I'm here to help!

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: 0

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0759d9e and ed26a6a.

Files selected for processing (1)
  • sonar-project.properties (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • sonar-project.properties

@@ -6,7 +6,7 @@ sonar.project.monorepo.enabled=true

sonar.sources=.
sonar.exclusions=**/*_test.go,**/*.pb.go,**/*.pulsar.go,**/*.pb.gw.go
Copy link
Member

Choose a reason for hiding this comment

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

@tac0turtle tac0turtle enabled auto-merge May 31, 2024 20:52
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: 0

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ed26a6a and dfcc391.

Files selected for processing (1)
  • sonar-project.properties (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • sonar-project.properties

@tac0turtle tac0turtle added this pull request to the merge queue May 31, 2024
Merged via the queue into main with commit fda440d May 31, 2024
61 checks passed
@tac0turtle tac0turtle deleted the marko/cleanup_sonar branch May 31, 2024 21:10
alpe added a commit that referenced this pull request Jun 3, 2024
* main:
  docs: add docs on permissions (#20526)
  refactor(x/gov): set environment in context for legacy proposals (#20521)
  docs: migrate diagrams to mermaidjs (#20503)
  refactor(tools/hubl): don't use nil panic (#20515)
  refactor(x/authz): set environment in context (#20502)
  build(deps): Bump github.com/spf13/viper from 1.18.2 to 1.19.0 (#20519)
  feat(x/bank): Placing SendRestriction before Deduction of Coins in SendCoins (#20517)
  chore: sonar ignore directories with their own go.mods  (#20509)
  ci: run action in merge queue (#20508)
alpe added a commit that referenced this pull request Jun 3, 2024
* main:
  refactor(x/feegrant): set environment in context (#20529)
  refactor(x/accounts)!: accounts and auth module use the same account number tracking (#20405)
  chore: remove sonar from simapp (#20528)
  docs: add docs on permissions (#20526)
  refactor(x/gov): set environment in context for legacy proposals (#20521)
  docs: migrate diagrams to mermaidjs (#20503)
  refactor(tools/hubl): don't use nil panic (#20515)
  refactor(x/authz): set environment in context (#20502)
  build(deps): Bump github.com/spf13/viper from 1.18.2 to 1.19.0 (#20519)
  feat(x/bank): Placing SendRestriction before Deduction of Coins in SendCoins (#20517)
  chore: sonar ignore directories with their own go.mods  (#20509)
  ci: run action in merge queue (#20508)
  refactor(server/v2/cometbft): update function comments (#20506)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants