chore: fix gosec G115 linting issues for Go 1.24.1 update #17084
Conversation
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
Added more detailed #nosec G115 annotations to fix gosec warnings 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Fix go:build directive spacing in pty_linux.go - Add bounds checks and #nosec annotations for integer conversions - Fix comment alignment and formatting - Address gosec G115 warnings in multiple files Co-Authored-By: Claude <noreply@anthropic.com>
|
I have read the CLA Document and I hereby sign the CLA 0 out of 2 committers have signed the CLA. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds detailed #nosec G115 annotations to resolve gosec linting issues for the Go 1.24.1 upgrade in PR #17035.
This PR adds proper annotations with detailed comments to explain why each integer conversion is safe, which helps the linter understand that these conversions are intentional and the potential overflow risks are handled appropriately.
Part of the work for #17035.