Skip to content

Conversation

@sparrc
Copy link
Contributor

@sparrc sparrc commented Dec 21, 2024

Summary

Issue #, if available:

Testing

make debug succeeded:
Integ tests succeeded:
New tests cover the changes:

Description for the changelog

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@sparrc sparrc requested a review from a team as a code owner December 21, 2024 16:35
func getS3Object(s3Client *s3.S3, input *s3.GetObjectInput) *s3.GetObjectOutput {
obj, err := s3Client.GetObject(input)

func processFile(file *os.File, filePath string) (int, error) {
Copy link
Contributor

Choose a reason for hiding this comment

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

not sure where this function is used.

Copy link
Contributor

@swapneils swapneils left a comment

Choose a reason for hiding this comment

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

All non-blocking comments, so merging for now to unblock the current CVE release. Please respond/address-in-a-followup-PR when you can.

break
}
if err != nil {
fmt.Println("[TEST ERROR] Malform log entry. Unmarshal Error:", err)
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we no longer printing the failing entry?

s3RecordCounter++
value, err := strconv.ParseUint(recordId, 10, 32)
if err != nil {
fmt.Println("[TEST ERROR] Malform log entry. ParseUint Error:", err)
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious, why are we parsing the recordId now instead of using the raw value?

continue
}
recordIdUint := uint32(value)
inputMap[recordIdUint] = struct{}{}
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: Does this value need to be a struct, or would a true provide the same results? Seems the latter would be more memory-efficient.

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.

3 participants