When very large numbers of diff present: "comm" error #7
Description
Possible bug in sorting implementation/overflow:
When scanning a folder with >10k known changes, the following message is occasionally seen in the Modified section of the output:
comm: input is not in sorted order
ACTION: investigate sort calls and make sure diff calls are set to check/ignore sort appropriately
SCOPE: this has only been seen once, when scanning a folder with over 10k known path changes. Likely caused by a unicode/diacritic character in the file path that threw off sort. Behavior has not been seen since, but creating this issue while I investigate inline with other enhancements and bug fixes. :)