Tree: 7782f6146e

master

4.2.6

4.2.4

4.2.3

5.0.0-rc9

5.0.0-rc8

5.0.0-rc7

5.0.0-rc6

5.0.0-rc5

5.0.0-rc4

5.0.0-rc3

5.0.0-rc2

5.0.0-rc1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '7782f6146e'

${ noResults }

Commit Graph

2 Commits (7782f6146e8c078661f21ef67d4130cf737100b0)

Author	SHA1	Message	Date
Raimund Andree	ad899940ea	fix: write no Get-FileHash2 result for a file that could not be read Found while fixing defect 3, in the same loop: the hash variable lived outside the loop, and after a GetHashError the cmdlet still wrote a result for the file, with the hash of the previous file. Each path now starts without a hash, and a failed read writes only the error. Tests/FileHash.Tests.ps1: 1 test with a file opened without sharing; like the other Get-FileHash2 tests, it skips in PowerShell 7 until the RIPEMD160 reference goes (decision D5). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>	4 weeks ago
Raimund Andree	7f625a168b	fix: skip folders in Get-FileHash2 and hash the remaining paths Defect 3. Get-FileHash2 left ProcessRecord at the first folder in -Path, so the files that followed the folder in the same array were not hashed. It now skips the folder, like Get-FileHash, and continues. Tests/FileHash.Tests.ps1 (new): 1 test. It skips in PowerShell 7, where every Get-FileHash2 call fails until the RIPEMD160 reference goes (decision D5, later in this run). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>	4 weeks ago