-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add tests for common.go #5191
base: main
Are you sure you want to change the base?
Add tests for common.go #5191
Conversation
- ListPackagesByRepository() - GetArtifactVersions() - getPackageVersions()
- IsMinderHook() - CreateHook()
- CanHandleOwner() - NewFallbackTokenClient()
- StartCheckRun() - UpdateCheckRun()
- ListFiles() - ListAllRepositories()
- CreateSecurityAdvisory() - CloseSecurityAdvisory()
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.
Nice! I just had 1 non-blocking question.
} | ||
} | ||
|
||
func safeInt32(n int) int32 { |
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.
Is this necessary given that the integers are provided by us, so we know they will be within the bounds?
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.
Fair point, thanks -- removed
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.
ah, I remember why I added them now: the gosec linter was complaining about int overflow. Added a nolint now.
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.
Would it also work to change the type of tt.itemsPerPage
and tt.pageNumber
to int32
?
Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
Part of #4380
Note: The tests are broken down into different commits, based on their logical coverage.
Change Type
Mark the type of change your PR introduces:
Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist: