Skip to content

[v10.x backport] test: refactor common.ddCommand() #23630

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.

Sign up for GitHub

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

Closed
Trott wants to merge 16 commits into from
Closed

[v10.x backport] test: refactor common.ddCommand() #23630

Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
6d151ad
tls: make StreamWrap work correctly in "drain" callback
oyyd Oct 7, 2018
f2b4734
src: revert removal of SecureContext `_external` getter
dyatlov Jul 8, 2018
ad59bbd
lib: http server, friendly error messages
sagitsofan Sep 20, 2018
736d6d1
src: improve SSL version extraction logic
gireeshpunathil Sep 24, 2018
2218a38
src: fix bug in MallocedBuffer constructor
tniessen Oct 12, 2018
4b0c0f1
doc: revise security-reporting text in README
Trott Oct 10, 2018
f6a2af5
test: fixing assertion value order
joesepi Oct 12, 2018
4089a55
test: fix assert.strictEqual argument order
et4891 Oct 12, 2018
584470c
test: improve test-gc-http-client-connaborted
lundibundi Oct 1, 2018
0d7328d
test: improve test-gc-http-client-onerror
lundibundi Oct 1, 2018
35f9218
test: move some gc tests back to parallel/, unmark flaky
addaleax Oct 9, 2018
e86b6aa
zlib: generate error code names in C++
addaleax Oct 7, 2018
3a533d6
doc: describe SNI host name format
sam-github Oct 9, 2018
7c9b37e
http: reduce duplicated code for cleaning parser
starkwang Oct 9, 2018
79a2b00
test: refactor common.ddCommand()
Trott Oct 10, 2018
ea510a6
test: rename common.ddCommand()
Trott Oct 10, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
doc: revise security-reporting text in README 
Simplify and clarify the security-reporting text in the README. Now is
also probably a good time to ping the security triage folks to make sure
the text is still accurate.

PR-URL: #23407
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Yuta Hiroto <hello@hiroppy.me>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
  • Loading branch information
@Trott
Trott committed Oct 13, 2018
commit 4b0c0f19e4222f00734fff656c80a384460244a9
11 changes: 5 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,13 +159,12 @@ source and a list of supported platforms.

## Security

Security flaws in Node.js should be reported by emailing security@nodejs.org.
Please do not disclose security bugs publicly until they have been handled by
the security team.
If you find a security vulnerability in Node.js, please report it to
security@nodejs.org. Please withhold public disclosure until after the security
team has addressed the vulnerability.

Your email will be acknowledged within 24 hours, and you will receive a more
detailed response to your email within 48 hours indicating the next steps in
handling your report.
The security team will acknowledge your email within 24 hours. You will receive
a more detailed response within 48 hours.

There are no hard and fast rules to determine if a bug is worth reporting as
a security issue. The general rule is an issue worth reporting should allow an
Expand Down