Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: common.fixturesDir --> common.fixtures #15976

Conversation

camantigue
Copy link

@camantigue camantigue commented Oct 6, 2017

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
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

paulcamantigue-kaiser and others added 4 commits January 23, 2017 19:35
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
@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Oct 6, 2017
const net = require('net');

const sent = 'hello world';
let received = '';

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'),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could be using method fixtures.readKey instead to get the keys.

@mscdex mscdex added the tls Issues and PRs related to the tls subsystem. label Oct 6, 2017
@Trott Trott added the code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. label Oct 7, 2017
Copy link
Member

@BridgeAR BridgeAR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs a rebase and a force push before this can be landed (there are merge commits in here). LGTM otherwise.

@@ -24,17 +24,18 @@ const common = require('../common');
if (!common.hasCrypto)
common.skip('missing crypto');


Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit - it would be nice not to have any unrelated changes and if this could be changed back again.

@apapirovski
Copy link
Member

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 :)

@camantigue
Copy link
Author

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?

@apapirovski
Copy link
Member

@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.

Utilized the fixtures module's readKey function instead of readSync and removed an unnecessary line of space.
const net = require('net');

const sent = 'hello world';
let received = '';

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'),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This actually doesn't need /keys/ because the readKey already knows where to look.

@apapirovski
Copy link
Member

apapirovski commented Oct 20, 2017

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 .

@camantigue
Copy link
Author

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.

Removed `/keys/` from the key file path string as the readKey function handles that for you.
@tniessen
Copy link
Member

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

@apapirovski
Copy link
Member

@tniessen tniessen self-assigned this Oct 20, 2017
@joyeecheung
Copy link
Member

Landed in c4c6381, thank you for the contribution!

joyeecheung pushed a commit that referenced this pull request Oct 21, 2017
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>
@joyeecheung
Copy link
Member

joyeecheung commented Oct 21, 2017

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)

@camantigue
Copy link
Author

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.

@joyeecheung
Copy link
Member

joyeecheung commented Oct 21, 2017

@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.

@camantigue
Copy link
Author

camantigue commented Oct 21, 2017

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.

@gibfahn
Copy link
Member

gibfahn commented Oct 22, 2017

Let me know if anything else is needed for the promotion.

@camantigue looks like GitHub noticed, and updated accordingly, congratulations on becoming a contributor to Node.js!

image

MylesBorins pushed a commit that referenced this pull request Oct 23, 2017
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>
addaleax pushed a commit to ayojs/ayo that referenced this pull request Oct 26, 2017
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>
MylesBorins pushed a commit that referenced this pull request Nov 16, 2017
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>
@MylesBorins MylesBorins mentioned this pull request Nov 21, 2017
MylesBorins pushed a commit that referenced this pull request Nov 21, 2017
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>
MylesBorins pushed a commit that referenced this pull request Nov 28, 2017
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>
addaleax pushed a commit to ayojs/ayo that referenced this pull request Dec 7, 2017
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. test Issues and PRs related to the tests. tls Issues and PRs related to the tls subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.