FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

tls: introduce ERR_TLS_INVALID_CONTEXT by Trott · Pull Request #30718 · nodejs/node · GitHub

/ node Public

tls: introduce ERR_TLS_INVALID_CONTEXT - #30718

Closed
Trott wants to merge 0 commit into
nodejs:masterfrom
Trott:not-internal
Closed

tls: introduce ERR_TLS_INVALID_CONTEXT#30718
Trott wants to merge 0 commit into
nodejs:masterfrom
Trott:not-internal

Conversation

Trott commented Nov 29, 2019

Copy link
Copy Markdown
Member

It is trivially possible to cause an internal assertion error with
tls.createSecurePair(). Throw a friendly error instead. Reserve internal
assertions for things that we believe to be impossible.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

nodejs-github-bot added errors Issues and PRs related to JavaScript errors originated in Node.js core. tls Issues and PRs related to the tls subsystem. labels Nov 29, 2019
Trott added the semver-major PRs that contain breaking changes and should be released in the next major version. label Nov 29, 2019

This comment has been minimized.

Trott added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Nov 29, 2019

Trott commented Nov 29, 2019

Copy link
Copy Markdown
Member Author

addaleax removed the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Nov 29, 2019

addaleax left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This doesn’t have to be semver-major, imo

Comment thread doc/api/errors.md Outdated
Trott removed the semver-major PRs that contain breaking changes and should be released in the next major version. label Nov 30, 2019

Copy link
Copy Markdown
Collaborator

Comment thread lib/internal/errors.js Outdated
Trott added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Nov 30, 2019

nodejs-github-bot commented Nov 30, 2019
edited by Trott
Loading

Copy link
Copy Markdown
Collaborator

Trott added a commit to Trott/io.js that referenced this pull request Dec 1, 2019
It is trivially possible to cause an internal assertion error with
tls.createSecurePair(). Throw a friendly error instead. Reserve internal
assertions for things that we believe to be impossible.

PR-URL: nodejs#30718
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
Trott closed this Dec 1, 2019

Trott commented Dec 1, 2019

Copy link
Copy Markdown
Member Author

Landed in d25db11

Trott deleted the not-internal branch December 1, 2019 20:08
targos pushed a commit that referenced this pull request Dec 2, 2019
It is trivially possible to cause an internal assertion error with
tls.createSecurePair(). Throw a friendly error instead. Reserve internal
assertions for things that we believe to be impossible.

PR-URL: #30718
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
BridgeAR mentioned this pull request Dec 3, 2019
targos pushed a commit that referenced this pull request Jan 13, 2020
It is trivially possible to cause an internal assertion error with
tls.createSecurePair(). Throw a friendly error instead. Reserve internal
assertions for things that we believe to be impossible.

PR-URL: #30718
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
BethGriggs pushed a commit that referenced this pull request Feb 6, 2020
It is trivially possible to cause an internal assertion error with
tls.createSecurePair(). Throw a friendly error instead. Reserve internal
assertions for things that we believe to be impossible.

PR-URL: #30718
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
MylesBorins mentioned this pull request Feb 8, 2020
This file contains hidden or 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
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 outstanding review comments, and a CI started. errors Issues and PRs related to JavaScript errors originated in Node.js core. tls Issues and PRs related to the tls subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants


Back | FazBrowse Home | New Git URL