Skip to content

chore(lint): enable errcheck and fix test-file findings#1774

Draft
AmanGIT07 wants to merge 1 commit into
mainfrom
chore/enable-errcheck-linter
Draft

chore(lint): enable errcheck and fix test-file findings#1774
AmanGIT07 wants to merge 1 commit into
mainfrom
chore/enable-errcheck-linter

Conversation

@AmanGIT07

Copy link
Copy Markdown
Contributor

Summary

Enable the errcheck linter and fix the findings that live in test files. Final piece of the errcheck rollout.

Depends on #1768, #1769, #1770, #1771, #1773 — the lint job stays red until they merge; this branch then gets rebased and marked ready.

Changes

  • Add errcheck to linters.enable in .golangci.yml
  • internal/api/v1beta1connect/authenticate_test.go: _ = on 12 JWK fixture calls (no t in scope inside the fixture closures); require.NoError on the json.Unmarshal that builds an expected value
  • internal/store/postgres/prospect_repository_test.go: assert the between-case s.cleanup() so a failed cleanup stops the suite at the real problem
  • pkg/server/webhook_bridge_test.go: _, _ = on two stub-handler writes
  • test/e2e/regression/authentication_test.go: nolint on the callback server shutdown defer

Test Plan

  • go test ./internal/api/v1beta1connect/ ./pkg/server/ and the prospect suite pass
  • golangci-lint run with errcheck enabled reports zero findings in test files; the remaining findings are exactly the sites fixed by the five PRs above

Turn on errcheck in golangci and resolve the seventeen findings in test
files: blank-assign fixture setup calls without a test handle in scope,
and assert the ones that feed expected values or reset shared state.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
frontier Ready Ready Preview, Comment Jul 18, 2026 6:18am

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 66565f3c-f010-4a30-88a8-960b5f55d4b6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 29633761765

Coverage remained the same at 46.11%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 38321
Covered Lines: 17670
Line Coverage: 46.11%
Coverage Strength: 13.32 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants