roymalhi

The issue was caused by the default behavior of git on windows , it has autocrlf on by default for text files. We package our dcc apps in tagged repos and whilst the runprocedurals.py was correct in the repository, upon localization of the package, on checkout , git converted the line endings form lf to crlf and the checksum thus failed because the hash returned would have been different with crlf line endings.
This is an edge case , but if you want to make sure it doesn’t happen again or at lease be more specific about the error message when the checksum fails, you already check if it’s windows I believe as part of the hash test , so check for unexpected line endings and print it as part of the error , or better yet, allow crlf resolved hash on windows as well as lf . But it’s no longer an issue for us, once I realized what it was , I just changed the git config and problem solved . Thank you for your attention to this issue

We discovered that is was the line endings on windows crlf vs lf that husk is expecting when testing the hash

Thank you, I did log a bug report, but I'm also trying to understand if something is going on with our system. we've never used 19.5.557. As I understand it husk sees runprocedurals.py for some reason as different to what husk expects and the hash verification fails?