| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
fix description about crypto.randomBytes
There was a problem hiding this comment.
I don't think that's very enlightening for people not familiar with openssl or the code base. I don't really have suggestions on how to reword it, just that it's not very helpful now (and the part about CheckEntropy() is arguably wrong in a nuanced way.)
Also, please wrap lines at 80 columns.
Sorry, something went wrong.
There was a problem hiding this comment.
Perhaps, @JungMinu, you could update the code block instead? The note is mostly correct about the current behavior. Maybe remove the try / catch block in the example?
Sorry, something went wrong.
|
The commit log could be be a little more descriptive. Ideally, you shouldn't have to look at the diff to know what a commit changed. |
Sorry, something went wrong.
|
@bnoordhuis Thanks, I will update |
Sorry, something went wrong.
|
@brendanashworth Thanks for your comment, I would love to 😄 |
Sorry, something went wrong.
|
@JungMinu assuming you've setup locally with git, you can always add new changes as new commits and push them to github. It will automatically update this PR, which is easier for everyone. |
Sorry, something went wrong.
remove outdated examples about crypto.randomBytes to make it clear
|
@brendanashworth Based on your comments, I removed try / catch block. |
Sorry, something went wrong.
|
@brendanashworth @bnoordhuis Please review |
Sorry, something went wrong.
|
I speculate that @brendanashworth's suggestion was to remove the try/catch statement, not the call to crypto.randomBytes(). |
Sorry, something went wrong.
fix outdated examples about crypto.randomBytes to make it clear
The code shows that it throws on a lack of entropy, but the note below says that it does not. Remove outdated `try/catch`statements in sync examples about crypto.randomBytes to make it clear
|
@bnoordhuis I've updated commit log and description, Thanks 😄 |
Sorry, something went wrong.
The code shows that it throws on a lack of entropy, but the note below says that it does not. Remove outdated try/catchstatements in sync examples about crypto.randomBytes to make it clear
The code shows that it throws on a lack of entropy, but the note below says that it does not. Remove outdated `try/catch`statements in sync examples about crypto.randomBytes to make it clear
There was a problem hiding this comment.
Does this mean there should be a try/catch? randomBytes() will never throw anymore, right?
Sorry, something went wrong.
The code shows that it throws on a lack of entropy, but the note below says that it does not. Remove outdated `try/catch`statements in sync examples about crypto.randomBytes to make it clear
|
@Fishrock123 Sorry, I made a mistake. |
Sorry, something went wrong.
|
@Fishrock123 Thanks for your comment 😄 |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Perfect, also LGTM! |
Sorry, something went wrong.
There was a problem hiding this comment.
May I suggest to use const?
Sorry, something went wrong.
|
LGTM with take-it or leave-it suggestion |
Sorry, something went wrong.
The code shows that it throws on a lack of entropy, but the note below says that it does not. Remove outdated try/catchstatements in sync examples about crypto.randomBytes to make it clear. In addition, use `const` instead of `var` for constant variable.
|
@thefourtheye Thanks, I've updated |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The code shows that it throws on a lack of entropy, but the note below says that it does not.
Remove outdated try/catchstatements in sync examples about crypto.randomBytes to make it clear