panicinlibrarycode: recognize sync.OnceValue/OnceFunc panic exemptions - #48956
Merged
pelikhan merged 2 commits intoJul 29, 2026
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix linter blind spot for sync.OnceValue/OnceFunc panics
panicinlibrarycode: recognize sync.OnceValue/OnceFunc panic exemptions
Jul 29, 2026
pelikhan
marked this pull request as ready for review
July 29, 2026 18:35
Contributor
There was a problem hiding this comment.
Pull request overview
Extends the panic linter’s sync.Once exemption to Go 1.21 lazy-initialization helpers.
Changes:
- Recognizes
sync.OnceValueandsync.OnceFunccallbacks. - Adds selector and generic-call handling.
- Adds focused analyzer test cases.
Show a summary per file
| File | Description |
|---|---|
pkg/linters/panic-in-library-code/panic-in-library-code.go |
Generalizes sync-once callback detection. |
pkg/linters/panic-in-library-code/testdata/src/panicinlibrarycode/panicinlibrarycode.go |
Tests OnceValue and OnceFunc exemptions. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Medium
| } | ||
|
|
||
| func isSyncOnceConstructorCall(pass *analysis.Pass, sel *ast.SelectorExpr) bool { | ||
| return isSyncPackageFunc(pass, sel, "OnceValue", "OnceFunc") |
Contributor
Triage: bug (linter fix)Risk: low | Priority: medium (score 48/100) Breakdown: impact 20/50 (narrow linter-analyzer scope, 2 files) · urgency 15/30 (CI fully green) · quality 13/20 (good description, has test data, no reviews yet) Recommended action: All CI checks passing. Small, well-scoped fix to panicinlibrarycode analyzer exemptions.
|
This was referenced Jul 29, 2026
Contributor
|
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
panicinlibrarycodeonly exemptedsync.Once.Do(func(){...})and missed equivalent Go 1.21+ lazy-init patterns (sync.OnceValue/sync.OnceFunc). That created a governance gap where exemption behavior depended on panic message text (BUG:) rather than call-site semantics.Analyzer exemption expansion
Once.Do-only to all supported sync-once initializer forms.sync.OnceValue/sync.OnceFunc/(*sync.Once).Do.Behavioral consistency
Once.Dohandling.Focused test coverage
sync.OnceValue(func() T { ... })sync.OnceFunc(func() { ... })BUG:panic messages to validate semantic exemption logic.