-
-
Notifications
You must be signed in to change notification settings - Fork 1k
fix: upx properly handle skips #5720
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
Conversation
Deploying goreleaser with
|
Latest commit: |
263d1f4
|
Status: | ✅ Deploy successful! |
Preview URL: | https://96fada05.goreleaser.pages.dev |
Branch Preview URL: | https://upx-fix.goreleaser.pages.dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
Files not reviewed (1)
- internal/pipe/upx/testdata/fakeupx: Language not supported
Comments suppressed due to low confidence (1)
internal/pipe/upx/upx.go:51
- [nitpick] The removal of launching a separate goroutine for each binary compressOne call now processes them sequentially. Confirm that this change is intentional, as it may impact performance when handling multiple binaries concurrently.
if err := compressOne(ctx, upx, bin); err != nil {
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
Files not reviewed (2)
- internal/pipe/upx/testdata/fakeupx: Language not supported
- www/docs/static/schema-pro.json: Language not supported
Comments suppressed due to low confidence (2)
internal/pipe/upx/upx.go:37
- The change from using semerrgroup.NewSkipAware to semerrgroup.New combined with a separate SkipMemento may affect the concurrency and skip aggregation behavior; please verify that this change fully aligns with the intended skip handling logic or add a clarifying comment.
g := semerrgroup.New(ctx.Parallelism)
internal/pipe/upx/upx.go:38
- [nitpick] Consider adding an inline comment to explain the purpose of using SkipMemento for accumulating skip events instead of returning immediately; this helps maintain clarity on the skip handling overall.
skips := pipe.SkipMemento{}
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5720 +/- ##
==========================================
- Coverage 82.99% 82.93% -0.07%
==========================================
Files 160 160
Lines 15758 15765 +7
==========================================
- Hits 13079 13075 -4
- Misses 2115 2124 +9
- Partials 564 566 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
closes #5719
upx
for real andgo build