-
Notifications
You must be signed in to change notification settings - Fork 30k
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: fix invalid argument order in test-http-expect-continue.js #24138
Closed
mroderick
wants to merge
1
commit into
nodejs:master
from
mroderick:fix-argument-order-http-expect-continue
Closed
test: fix invalid argument order in test-http-expect-continue.js #24138
mroderick
wants to merge
1
commit into
nodejs:master
from
mroderick:fix-argument-order-http-expect-continue
Conversation
This file contains 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
`assert.strictEqual` expects arguments in the following order: actual, expected[, message]
cjihrig
approved these changes
Nov 6, 2018
addaleax
approved these changes
Nov 6, 2018
addaleax
added
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.
labels
Nov 6, 2018
BridgeAR
approved these changes
Nov 6, 2018
trivikr
approved these changes
Nov 7, 2018
gireeshpunathil
approved these changes
Nov 7, 2018
pls thumbs up for fast tracking |
gireeshpunathil
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Nov 8, 2018
Trott
pushed a commit
to Trott/io.js
that referenced
this pull request
Nov 8, 2018
`assert.strictEqual` expects arguments in the following order: actual, expected[, message] PR-URL: nodejs#24138 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
Landed in 0dbbded. Thanks for the contribution! 🎉 (If you're interested in other possible contributions to Node.js but don't have a good idea of where to start looking, some ideas are posted at https://www.nodetodo.org/next-steps/.) |
BridgeAR
pushed a commit
that referenced
this pull request
Nov 14, 2018
`assert.strictEqual` expects arguments in the following order: actual, expected[, message] PR-URL: #24138 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
kiyomizumia
pushed a commit
to kiyomizumia/node
that referenced
this pull request
Nov 15, 2018
`assert.strictEqual` expects arguments in the following order: actual, expected[, message] PR-URL: nodejs#24138 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
This was referenced Nov 15, 2018
codebytere
pushed a commit
that referenced
this pull request
Dec 13, 2018
`assert.strictEqual` expects arguments in the following order: actual, expected[, message] PR-URL: #24138 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
MylesBorins
pushed a commit
that referenced
this pull request
Dec 26, 2018
`assert.strictEqual` expects arguments in the following order: actual, expected[, message] PR-URL: #24138 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]>
Merged
This was referenced Jan 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
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.
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.
assert.strictEqual
expects arguments in the following order:actual, expected[, message]
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes