Skip to content

[-] fix linter warning "impossible condition: nil != nil" #652

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Feb 17, 2025
Merged

[-] fix linter warning "impossible condition: nil != nil" #652

merged 1 commit into from
Feb 17, 2025

Conversation

pashagolub
Copy link
Collaborator

No description provided.

@pashagolub pashagolub self-assigned this Feb 17, 2025
@pashagolub pashagolub added the enhancement New feature or request label Feb 17, 2025
@coveralls
Copy link

Pull Request Test Coverage Report for Build 13376125251

Details

  • 0 of 2 (0.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 30.413%
Changes Missing Coverage Covered Lines Changed/Added Lines %
internal/metrics/psutil/psutil.go 0 2 0.0%
Totals Coverage Status
Change from base Build 13375784960: 0.0%
Covered Lines: 1489
Relevant Lines: 4896
💛 - Coveralls

@pashagolub pashagolub merged commit 1c9eef9 into master Feb 17, 2025
8 checks passed
@pashagolub pashagolub deleted the linter-nilness branch February 17, 2025 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@pashagolub pashagolub

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@pashagolub @coveralls