Hash is wrong if the file is "big" #30
Comments
itnok
added a commit
to itnok/grunt-rev
that referenced
this issue
Mar 20, 2015
…orrectly calculated) The `fs` library is already included and it looks like it works better than `grunt.file`. With files bigger than few kilobytes the hash is calculated in the right way. It looks like `grunt.file.read` either does not read the file correctly or not in full. This change solves Issue sebdeckers#30
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On "big" files (I am having this problem on a Js file just slightly bigger than 1MB) the calculated hash is definitely wrong.
With smaller files no problem though.
Is it possible that if a file is big enough only a chunk of the file is used?
On my file, for example, these are the results:
options: {algorithm: md5, length: 32}):9e494b97b63d7e67833df32376b4bb2bcat scripts.min.js | openssl md5:36cd285cd1271348628d496c3735b179The text was updated successfully, but these errors were encountered: