actual hash value not recorded in log
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
I'm encountering an issue with a package (or the download) where it would be handy to see if the checksums of the downloaded file is consistent. There is a console message:
> Error - hashes do not match. Actual value was '[hash]'
but once the console closes (or the buffer fills) that information is gone. I can find multiple references in the logs for what the checksum should be, but it appears the actual value is never recorded.
Can that line be included in the log?
Thanks.
Contributor guide
Research direction
No files or tests are named. Start by locating the console message for the hash mismatch and trace how that message is emitted versus the logging path. Done means the actual hash value is also recorded in the log when checksums do not match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100