Skip to content

Conversation

@Trott
Copy link
Member

@TrottTrott commented Nov 19, 2022

This reverts commit 5f7730e.

This change broke too many edge cases in the ecosystem. Reverting it re-introduces some host-spoofing possibilities, so we won't want to revert forever, but the issue has been around for a long time and we can wait for a major release to introduce the fix as a breaking change. After this lands, I plan to re-introduce this as a change that throws a warning rather than an error, after which we can land a semver-major that re-introduces the error and try to get the word out to maintainers of likely-affected packages.

Closes: #45514
Refs: #45012

This reverts commit 5f7730e. This change broke too many edge cases in the ecosystem. Reverting it re-introduces some host-spoofing possibilities, so we won't want to revert forever, but the issue is long-lived enough and not sufficiently critical that we can't wait for a major release to introduce it as a breaking change. After this lands, I plan to re-introduce this as a change that throws a warning rather than an error, after which we can land a semver-major that re-introduces the error and try to get the word out to maintainers of likely-affected packages. Closes: nodejs#45514 Refs: nodejs#45012
@nodejs-github-botnodejs-github-bot added needs-ci PRs that need a full CI run. url Issues and PRs related to the legacy built-in url module. labels Nov 19, 2022
@Trott
Copy link
MemberAuthor

@ljharb@merceyz

@TrottTrott added the request-ci Add this label to start a Jenkins CI on a PR. label Nov 19, 2022
@github-actionsgithub-actionsbot removed the request-ci Add this label to start a Jenkins CI on a PR. label Nov 19, 2022
@nodejs-github-bot
Copy link
Collaborator

@richardlau
Copy link
Member

Since this is a revert, setting the same don't-land labels as #45012.

@ljharb
Copy link
Member

Thanks!

@nodejs-github-bot
Copy link
Collaborator

@TrottTrott added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. labels Nov 19, 2022
@TrottTrott added the fast-track PRs that do not need to wait for 48 hours to land. label Nov 19, 2022
@github-actions
Copy link
Contributor

Fast-track has been requested by @Trott. Please 👍 to approve.

@nodejs-github-botnodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Nov 19, 2022
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/45517 ✔ Done loading data for nodejs/node/pull/45517 ----------------------------------- PR info ------------------------------------ Title Revert "url: improve port validation" (#45517) Author Rich Trott (@Trott) Branch Trott:revert-it -> nodejs:main Labels url, fast-track, author ready, needs-ci, dont-land-on-v14.x, dont-land-on-v16.x, dont-land-on-v18.x Commits 1 - Revert "url: improve port validation" Committers 1 - Rich Trott PR-URL: https://github.com/nodejs/node/pull/45517 Fixes: https://github.com/nodejs/node/issues/45514 Refs: https://github.com/nodejs/node/pull/45012 Reviewed-By: James M Snell Reviewed-By: Richard Lau Reviewed-By: Yagiz Nizipli ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/45517 Fixes: https://github.com/nodejs/node/issues/45514 Refs: https://github.com/nodejs/node/pull/45012 Reviewed-By: James M Snell Reviewed-By: Richard Lau Reviewed-By: Yagiz Nizipli -------------------------------------------------------------------------------- ℹ This PR was created on Sat, 19 Nov 2022 14:23:45 GMT ✔ Approvals: 3 ✔ - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/45517#pullrequestreview-1187082412 ✔ - Richard Lau (@richardlau) (TSC): https://github.com/nodejs/node/pull/45517#pullrequestreview-1187082570 ✔ - Yagiz Nizipli (@anonrig): https://github.com/nodejs/node/pull/45517#pullrequestreview-1187100493 ℹ This PR is being fast-tracked ✖ The fast-track request requires at least two collaborators' approvals (👍). ✔ Last GitHub CI successful ℹ Last Full PR CI on 2022-11-19T15:29:52Z: https://ci.nodejs.org/job/node-test-pull-request/48018/ - Querying data for job/node-test-pull-request/48018/ ✔ Last Jenkins CI successful -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/3504637731

@nodejs-github-botnodejs-github-bot added the commit-queue-failed An error occurred while landing this pull request using GitHub Actions. label Nov 19, 2022
@aduh95aduh95 added the commit-queue Add this label to land a pull request using GitHub Actions. label Nov 19, 2022
@nodejs-github-botnodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Nov 19, 2022
@nodejs-github-botnodejs-github-bot merged commit bd965aa into nodejs:mainNov 19, 2022
@nodejs-github-bot
Copy link
Collaborator

Landed in bd965aa

@TrottTrott deleted the revert-it branch November 19, 2022 20:07
ruyadorno pushed a commit that referenced this pull request Nov 21, 2022
This reverts commit 5f7730e. This change broke too many edge cases in the ecosystem. Reverting it re-introduces some host-spoofing possibilities, so we won't want to revert forever, but the issue is long-lived enough and not sufficiently critical that we can't wait for a major release to introduce it as a breaking change. After this lands, I plan to re-introduce this as a change that throws a warning rather than an error, after which we can land a semver-major that re-introduces the error and try to get the word out to maintainers of likely-affected packages. Closes: #45514 Refs: #45012 PR-URL: #45517Fixes: #45514 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
marco-ippolito pushed a commit to marco-ippolito/node that referenced this pull request Nov 23, 2022
This reverts commit 5f7730e. This change broke too many edge cases in the ecosystem. Reverting it re-introduces some host-spoofing possibilities, so we won't want to revert forever, but the issue is long-lived enough and not sufficiently critical that we can't wait for a major release to introduce it as a breaking change. After this lands, I plan to re-introduce this as a change that throws a warning rather than an error, after which we can land a semver-major that re-introduces the error and try to get the word out to maintainers of likely-affected packages. Closes: nodejs#45514 Refs: nodejs#45012 PR-URL: nodejs#45517Fixes: nodejs#45514 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
@ruyadornoruyadorno mentioned this pull request Nov 24, 2022
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.commit-queue-failedAn error occurred while landing this pull request using GitHub Actions.fast-trackPRs that do not need to wait for 48 hours to land.needs-ciPRs that need a full CI run.urlIssues and PRs related to the legacy built-in url module.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

node 19.1 breaks url.parse

7 participants

@Trott@nodejs-github-bot@richardlau@ljharb@jasnell@anonrig@aduh95