| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Replaced `common.fixturesDir` with usage of `common.fixtures` module in `test/parallel/test-tls-delayed-atach.js`. Checklist [*] `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes
| const options = { | ||
| key: fs.readFileSync(`${common.fixturesDir}/keys/agent1-key.pem`), | ||
| cert: fs.readFileSync(`${common.fixturesDir}/keys/agent1-cert.pem`) | ||
| key: fixtures.readSync('/keys/agent1-key.pem'), |
There was a problem hiding this comment.
This could be using method fixtures.readKey instead to get the keys.
Sorry, something went wrong.
There was a problem hiding this comment.
This needs a rebase and a force push before this can be landed (there are merge commits in here). LGTM otherwise.
Sorry, something went wrong.
| if (!common.hasCrypto) | ||
| common.skip('missing crypto'); | ||
|
|
||
|
|
There was a problem hiding this comment.
Nit - it would be nice not to have any unrelated changes and if this could be changed back again.
Sorry, something went wrong.
|
Hi @camantigue — are you still interested in pursuing this? It looks like there's a bit of feedback from @BridgeAR & @pawelgolda that needs to be addressed. Let us know if you need any pointers :) |
Sorry, something went wrong.
|
Hi @apapirovski - I'm still interested in updating the changes. Is it just re-doing it without the merge commits? Or is it also preferred to use fixtures.readKey for line 37? |
Sorry, something went wrong.
|
@camantigue Ideally we would update to use fixtures.readKey like so fixtures.readKey('agent1-key.pem'). Also if you could remove the extra line break @BridgeAR mentioned, that would be appreciated. |
Sorry, something went wrong.
Utilized the fixtures module's readKey function instead of readSync and removed an unnecessary line of space.
| const options = { | ||
| key: fs.readFileSync(`${common.fixturesDir}/keys/agent1-key.pem`), | ||
| cert: fs.readFileSync(`${common.fixturesDir}/keys/agent1-cert.pem`) | ||
| key: fixtures.readKey('/keys/agent1-key.pem'), |
There was a problem hiding this comment.
This actually doesn't need /keys/ because the readKey already knows where to look.
Sorry, something went wrong.
|
If you're having trouble rebasing this, let us know. Since some of these merges are quite far in the past you might need to go quite far in history for your git rebase -i . |
Sorry, something went wrong.
|
Hi @apapirovski - How can I go about rebasing this? I don't think I've had experience doing that. Making the changes for the /keys/ right now. |
Sorry, something went wrong.
Removed `/keys/` from the key file path string as the readKey function handles that for you.
|
First, you need to add the upstream remote, fetch our current master and checkout your branch. Skip this section if you already did this: git remote add upstream https://github.com/nodejs/node.git git fetch upstream master git checkout change-test-parallel-delayed-attach-fixtures To rebase, do this: git rebase upstream/master If you run into problems while rebasing due to the merge commits, you can also cherry-pick your changes: git reset --hard upstream/master git cherry-pick 778fbdd071829fc245df7388fa5edc47828a4489 git cherry-pick 0414bced86075a461a63c4c942add3a1d9ede76a git cherry-pick 15579d4b30a78b97c791ae1d85d5643c9cdcb2f3 git cherry-pick c21f0b23da3788633cf7aede0a49e29d5c11ba6f |
Sorry, something went wrong.
Sorry, something went wrong.
|
Landed in c4c6381, thank you for the contribution! |
Sorry, something went wrong.
PR-URL: #15976 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
|
Hi @camantigue, the email that you used when authoring the commit is not added to your github account, so you are not promoted to "Contributor" after the commit landed. If you want the promotion, please add your email to your github account (the commit email is Paul-Marion.F.Camantigue@kp.org) |
Sorry, something went wrong.
|
Hi @joyeecheung this account (@camantigue) has my e-mail set as paulcamantigue@gmail.com and when I try to add the e-mail to the @paulcamantigue-kaiser account it states that my e-mail is already in use, which makes sense. How can I fix this? Hopefully won't have to put a dummy e-mail in this account and replace the Paul-Marion.F.Camantigue@kp.org with my paulcamantigue@gmail.com. |
Sorry, something went wrong.
|
@camantigue I think you can put a dummy email in @paulcamantigue-kaiser and add Paul-Marion.F.Camantigue@kp.org to @camantigue? Assuming you don't really use @paulcamantigue-kaiser anymore. |
Sorry, something went wrong.
|
Hey @joyeecheung I just changed the e-mail and it looks like the icons changed to my @camantigue account (I read your comment in #16360 haha). Let me know if anything else is needed for the promotion. |
Sorry, something went wrong.
@camantigue looks like GitHub noticed, and updated accordingly, congratulations on becoming a contributor to Node.js! |
Sorry, something went wrong.
PR-URL: #15976 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
PR-URL: nodejs/node#15976 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
PR-URL: #15976 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
PR-URL: #15976 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
PR-URL: #15976 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
PR-URL: nodejs/node#15976 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
| Back | FazBrowse Home | New Git URL |
Replaced common.fixturesDir with usage of common.fixtures module in
test/parallel/test-tls-delayed-atach.js.
Checklist