fix(auth): Changing variable from "MemoryCost" to "cpuMemCost" in standard_scrypt method #643
Conversation
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
RELEASE NOTE: Fixed an incorrect key used to set MemoryCost config in standard_scrypt() API
prameshj approved these changes Sep 8, 2022
| Can you fix the PR description? I think bug fix 489 is referring to a github issue in a different repo? |
pragatimodi changed the title prameshj approved these changes Sep 14, 2022
lahirumaramba changed the title Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
Changing the key value "MemoryCost" returned from standard_scrypt to "cpuMemCost"
RELEASE NOTE: Fixed an incorrect key used to set
memory_costconfig inauth.UserImportHash.standard_scrypt()API.