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

[v17.x] deps: update openssl to openssl-3.0.2+quic #42354

Closed

Conversation

hassaanp
Copy link
Contributor

Updated openssl dep to openssl-3.0.2+quic using the maintenance guide.

Refs: https://mta.openssl.org/pipermail/openssl-announce/2022-March/000217.html

tniessen and others added 30 commits February 7, 2022 23:29
Spelling out numbers makes this part easier to read. Also remove the
unnecessary word 'last'.

PR-URL: nodejs#41778
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Nitzan Uziely <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Refs: nodejs#39683

These are being worked, but we really should have
marked flaky a long time ago in ordert to make
then nightlies non-red.

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#41812
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: nodejs#41764
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
(Arguably, the whole terminology is not perfect, but at least it will be
consistent with TCP now.)

PR-URL: nodejs#41824
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Mestery <[email protected]>
PR-URL: nodejs#41799
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
This prepares us to enable the no-prototype-builtins ESLint rule.

Refs: https://eslint.org/docs/rules/no-prototype-builtins

PR-URL: nodejs#41801
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Mestery <[email protected]>
PR-URL: nodejs#41801
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Mestery <[email protected]>
PR-URL: nodejs#41827
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Beth Griggs <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Mestery <[email protected]>
PR-URL: nodejs#41797
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Gerhard Stöbich <[email protected]>
Reviewed-By: Vladimir de Turckheim <[email protected]>
made sure top level methods aren't async/generators
so that validation errors could be caught synchronously
also added validation for the abort signal option

PR-URL: nodejs#41777
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Nitzan Uziely <[email protected]>
PR-URL: nodejs#41478
Fixes: nodejs#41450
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Added imports for packages that is mentioned in the example of
async_hooks context example.

PR-URL: nodejs#39229
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Gerhard Stöbich <[email protected]>
PR-URL: nodejs#41814
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Tierney Cyren <[email protected]>
Original commit message:

    fix overflow check in error formatting

    Bug: v8:12494
    Change-Id: Iba2684173296aa236f1a1c73a5606c21472eff06
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3426634
    Reviewed-by: Jakob Kummerow <[email protected]>
    Commit-Queue: Gus Caplan <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#78909}

Refs: v8/v8@cc9a8a3

PR-URL: nodejs#41823
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Mary Marchini <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
When sending a continue request, server response with null,
it does not fires the response event type

Fixes: nodejs#38258

PR-URL: nodejs#41739
Refs: nodejs#38561
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Coverity was complaining that we did not check the
return code. We seem to check in the other place it
is called and the method already handles returning
a result.

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#41800
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
- document strategy based on Next-10 mini-summit
- initial top level info on http API implementations

Refs: nodejs/next-10#114

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#41798
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
PR-URL: nodejs#41841
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Added some hints that creation of an heap snapshot has significant
overhead on memory requirement and event loop utilization.

PR-URL: nodejs#41822
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Refs: nodejs#40823
Refs: nodejs#41113

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#41420
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Mary Marchini <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
PR-URL: nodejs#41817
Refs: https://coverage.nodejs.org/coverage-7123a00b03a90862/lib/readline/promises.js.html#L42
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Zijian Liu <[email protected]>
PR-URL: nodejs#41854
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Zijian Liu <[email protected]>
Reviewed-By: Mestery <[email protected]>
PR-URL: nodejs#41831
Refs: https://eslint.org/docs/rules/no-empty
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: nodejs#41831
Refs: https://eslint.org/docs/rules/no-empty
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: nodejs#41831
Refs: https://eslint.org/docs/rules/no-empty
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: nodejs#41831
Refs: https://eslint.org/docs/rules/no-empty
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: nodejs#41831
Refs: https://eslint.org/docs/rules/no-empty
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: nodejs#41831
Refs: https://eslint.org/docs/rules/no-empty
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Trott and others added 13 commits March 7, 2022 17:44
"considered undefined" suggests that it's not REALLY undefined. It's
really undefined. Be firm!

PR-URL: nodejs#42218
Reviewed-By: Akhil Marsonya <[email protected]>
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
PR-URL: nodejs#42190
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: nodejs#42238
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Make it always equals to `false`.

PR-URL: nodejs#42112
Reviewed-By: Darshan Sen <[email protected]>
Using `file://${path}` does not properly escape special URL characters.

PR-URL: nodejs#41758
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Juan José Arboleda <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
- update the messages to reflect additional
  bikeshedding that took place when action
  was implemented in
  https://github.com/nodejs/node/blob/master/.github/workflows/close-stale-feature-requests.yml.
- fix links to this document in messages as
  we moved the contributing docs location.

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#42217
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Notable changes:

* (SEMVER-MINOR) crypto: add KeyObject.prototype.equals method (Filip Skokan) nodejs#42093
* (SEMVER-MINOR) net: add new options to net.Socket and net.Server (Paolo Insogna) nodejs#41310
* (SEMVER-MINOR) src: allow preventing InitializeInspector in env (Shelley Vohr) nodejs#35025
* doc: add release key for Bryan English (Bryan English) nodejs#42102

Dependency Updates:

* deps: update nghttp2 to 1.47.0 (Yash Ladha) nodejs#42127
* deps: upgrade npm to 8.5.2 (npm team) nodejs#42122

New Collaborators:

* doc: add JakobJingleheimer to collaborators list (Jacob Smith) nodejs#42185
* doc: move bnoordhuis back to collaborators (Ben Noordhuis) nodejs#42064

PR-URL: nodejs#42254
This reverts commit 010cb71.

Refs: nodejs#42279

PR-URL: nodejs#42280
Fixes: nodejs#42279
Reviewed-By: Stewart X Addison <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Notable changes:

Fixed regression in url.resolve()

This release fixes an issue introduced in Node.js v17.7.0 with some URLs
that contain `@`. This issue affected yarn 1. This version reverts the
change that introduced the regression.

PR-URL: nodejs#42285
This updates all sources in deps/openssl/openssl by:
    $ git clone [email protected]:quictls/openssl.git
    $ cd openssl
    $ cd ../node/deps/openssl
    $ rm -rf openssl
    $ cp -R ../openssl openssl
    $ rm -rf openssl/.git* openssl/.travis*
    $ git add --all openssl
    $ git commit openssl
After an OpenSSL source update, all the config files need to be
regenerated and committed by:
    $ make -C deps/openssl/config
    $ git add deps/openssl/config/archs
    $ git add deps/openssl/openssl
    $ git commit
@nodejs-github-bot nodejs-github-bot added dependencies Pull requests that update a dependency file. needs-ci PRs that need a full CI run. openssl Issues and PRs related to the OpenSSL dependency. v17.x labels Mar 15, 2022
@richardlau
Copy link
Member

I think this should have been opened against master rather than v17.x-staging -- we should be able to cherry-pick openssl updates from master to current (v17.x-staging).

Last OpenSSL 3 update changes behaviour back to be
closer to that of OpenSSL 1.1.1. Remove some instances
where we expected different errors from OpenSSL 3 versus
OpenSSL 1.1.1.

Signed-off-by: Michael Dawson <[email protected]>
@mhdawson
Copy link
Member

It also needs a commit to fix up 2 failing tests. I'll push a commit to this branch with those fixes. It will cherrypick against master as well

@mhdawson
Copy link
Member

Pushed commit to fix the 2 tests I'd seen fail on master, in addition I think 17.x will need d4d0b09

@mhdawson
Copy link
Member

@hassaanp just to summarize what @richardlau suggested and related additional commits that will be needed for tests to pass

  1. The PR should be against master as that PR should be able to be cherry-picked cleanly to 17.x
  2. The PR I pushed onto this PR - d0b96b8 will also be needed in the PR on master. You should be able to cherry pick that from this PR to the PR against master

When the releaser builds 17.x they will need to cherry pick over the PRs to update OpenSSL, the PR to fix the tests and #42342. @danielleadams FYI since I think you are doing the 16.x and 17.x release

@hassaanp
Copy link
Contributor Author

@hassaanp just to summarize what @richardlau suggested and related additional commits that will be needed for tests to pass

  1. The PR should be against master as that PR should be able to be cherry-picked cleanly to 17.x
  2. The PR I pushed onto this PR - d0b96b8 will also be needed in the PR on master. You should be able to cherry pick that from this PR to the PR against master

When the releaser builds 17.x they will need to cherry pick over the PRs to update OpenSSL, the PR to fix the tests and #42342. @danielleadams FYI since I think you are doing the 16.x and 17.x release

Acknowledged @mhdawson.
I understand that I need to create a new PR against master. Does that mean I should I close this one then?

@RaisinTen
Copy link
Contributor

@hassaanp closing the PR shouldn't be necessary. You may click on the Edit button and change the base from v17.x-staging to master.

@hassaanp hassaanp changed the base branch from v17.x-staging to master March 16, 2022 04:39
@hassaanp
Copy link
Contributor Author

@RaisinTen I have changed the base like you suggested but it seems to have added a lot of conflicts. Any suggestions on how to proceed here?

@RaisinTen
Copy link
Contributor

You'll have to rebase and fix the git conflicts. Tbh, I think it would be easier to open a new PR.

@hassaanp
Copy link
Contributor Author

Yeah, I think that would be an easier route.
I am going to open a PR against master and we can then cherry pick the commits on to 17.x like @mhdawson and @richardlau suggested. Closing this one.

@hassaanp hassaanp closed this Mar 16, 2022
richardlau pushed a commit to nodejs/build that referenced this pull request Mar 16, 2022
Otherwise, the tests using OpenSSL as a shared library would fail on CI.

Refs: nodejs/node#42354 (comment)

Signed-off-by: Darshan Sen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file. needs-ci PRs that need a full CI run. openssl Issues and PRs related to the OpenSSL dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.