Bound member invocation logging argument strings#27511
Closed
KirtiRamchandani wants to merge 1 commit into
Closed
Conversation
Author
|
Closing in favor of replacement draft PR from neutral branch: #27513 |
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.
PR Summary
Bounds long string values included in member invocation logging while preserving the method invocation and recording the original string length.
PR Context
Addresses #21473.
MemberInvocationLoggingOps.ArgumentToString()currently returns full string arguments, soLogMemberInvocation()can build very large AMSI report content for calls such asFromBase64Stringwith large strings. This change keeps short strings unchanged, truncates long strings to 4096 characters, and appends a marker with the original length. It also applies the same bound to special primitive-likeToString()results, such as very largeBigIntegervalues.PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerValidation
Start-PSBuild -Clean -PSModuleRestore -UseNuGetOrgbuiltpwsh.exe. The first local build surfaced analyzer CA1845 for string construction; the patch was updated to use span-basedstring.Concat. The follow-up build producedpwsh.exe; the Windows PowerShell 5.1 build wrapper emitted post-buildConvertFrom-Json -Depthcompatibility warnings after build output was produced.Start-PSPester -Path test/powershell/engine/Logging/MemberInvocationLogging.Tests.ps1 -UseNuGetOrg -ThrowOnFailure -Terse -SkipTestToolBuildpassed: 2 passed, 0 failed.