Skip to content

Conversation

lukasschwab
Copy link
Contributor

@lukasschwab lukasschwab commented Feb 28, 2025

Eliminates duplicate implementation in package otel.
Copy link

codecov bot commented Feb 28, 2025

Codecov Report

Attention: Patch coverage is 85.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 83.69%. Comparing base (a4e0ea8) to head (e06b321).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
mocks.go 85.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #972      +/-   ##
==========================================
+ Coverage   83.65%   83.69%   +0.04%     
==========================================
  Files          49       50       +1     
  Lines        5139     5159      +20     
==========================================
+ Hits         4299     4318      +19     
- Misses        684      685       +1     
  Partials      156      156              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@cleptric
Copy link
Member

Could you fix the lint issue?

@lukasschwab
Copy link
Contributor Author

@cleptric if only it were that simple — the issue is the repo vars and secrets vars.SENTRY_RELEASE_BOT_CLIENT_ID and secrets.SENTRY_RELEASE_BOT_PRIVATE_KEY aren't provided to workflows triggered by PRs from forks.

Excerpt from the workflow run logs:

Screenshot 2025-03-13 at 4 56 24 PM

I can locally confirm I'm not introducing any lint issues.

$ # On the latest commit of my fork.
$ golangci-lint run ./... --sort-results --max-issues-per-linter=0 --max-same-issues=0 > "$(git rev-parse HEAD).txt"
$
$ # Reset to the merge-base state.
$ git reset --hard HEAD~
$ golangci-lint run ./... --sort-results --max-issues-per-linter=0 --max-same-issues=0 > "$(git rev-parse HEAD).txt"
$
$ # The only difference is a lint issue I *resolve* by deleting mocks_test.go.
$  diff bd1166f6bfd5e3f0841f43fd331df7eeee7e51b4.txt e56ac3010f8c48bbb32839ff8a7e751f420c361f.txt                                                              
72a73,75
> mocks_test.go:46:1: File is not properly formatted (gofmt)
>
> ^

If you want to verify — the commits in question are bd1166f and e56ac30. Here's a gist of the golangci-lint outputs.

@lukasschwab lukasschwab mentioned this pull request Mar 14, 2025
@lukasschwab lukasschwab marked this pull request as ready for review March 14, 2025 00:43
@lukasschwab
Copy link
Contributor Author

lukasschwab commented Mar 14, 2025

@cleptric I believe #981 would resolve this issue for future PRs.

Copy link
Member

@cleptric cleptric left a comment

Choose a reason for hiding this comment

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

Thanks!

@cleptric cleptric merged commit cfbfc6b into getsentry:master Mar 14, 2025
16 checks passed
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.

Expose MockTransport in a testhelpers package
2 participants