Bugfix for params arg ordering of maxmem and maxmemfrac to match documentation#165
Open
shanewholloway wants to merge 1 commit intobarrysteyn:masterfrom
Open
Bugfix for params arg ordering of maxmem and maxmemfrac to match documentation#165shanewholloway wants to merge 1 commit intobarrysteyn:masterfrom
maxmem and maxmemfrac to match documentation#165shanewholloway wants to merge 1 commit intobarrysteyn:masterfrom
Conversation
…` and `maxmemfrac` to match documentation Documentation lists the argument order of `scrypt.paramsSync` and `scrypt.params` as `maxtime, [maxmem, [max_memfrac]]`, and the argument checking in `index.js` is consistent with this. However, both `src/node-boilerplate/inc/scrypt_params_async.h` and `src/node-boilerplate/scrypt_params_sync.cc` were accessing the arguments as `[maxtime, max_memfrac, maxmem]`, and thus returning incorrect results.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation lists the argument order of
scrypt.paramsSyncandscrypt.paramsasmaxtime, [maxmem, [max_memfrac]], and the argumentchecking in
index.jsis consistent with this. However, bothsrc/node-boilerplate/inc/scrypt_params_async.handsrc/node-boilerplate/scrypt_params_sync.ccwere accessing the arguments as[maxtime, max_memfrac, maxmem], and thus returning incorrect results.