Initialize processor info memory to prevent garbage values#4871
Merged
Initialize processor info memory to prevent garbage values#4871
Conversation
mtfriesen
reviewed
Feb 27, 2025
anrossi
previously approved these changes
Feb 27, 2025
mtfriesen
previously approved these changes
Feb 27, 2025
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4871 +/- ##
==========================================
- Coverage 87.43% 86.07% -1.37%
==========================================
Files 56 56
Lines 17634 17630 -4
==========================================
- Hits 15419 15175 -244
- Misses 2215 2455 +240 ☔ View full report in Codecov by Sentry. |
guhetier
approved these changes
Feb 28, 2025
This was referenced Mar 9, 2026
Merged
ProjectsByJackHe
added a commit
that referenced
this pull request
Mar 13, 2026
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.
Description
The
PADDINGfield wasn't being set and apparently some code depended on that being explicitly zero.Testing
Ci/CD & Locally
Documentation
N/A