-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
Change type of LineNumber to ulong in Select-String #24075
Conversation
Very long files could overflow the LineNumber, leading to negative line numbers in output of Select-String. Changing to UInt64 should fix this for the forseeable future
|
We need WG conclusion and Committee approval for public API change. |
Anything I need to do? |
|
I'll queue this up for next WG review (1st Wed of the month) |
|
The @PowerShell/wg-powershell-cmdlets reviewed this. We believe this is a bucket 3 breaking change that is unlikely to impact real world usage. This would immediately address PowerShell script users and any unlikely C# usage would know how to fix their code to work against this change. |
|
📣 Hey @Snowman-25, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
|
@Snowman-25 Thanks for your contribution. |


Very long files could overflow the LineNumber, leading to negative line numbers in output of Select-String. Changing to UInt64 should fix this for the forseeable future
PR Summary
See Commit message: Fix for negative LineNumbers in Output of Select-String
PR Context
See Issue #24027
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.- [ ] Issue filed:
(which runs in a different PS Host).