Skip to content

Revert "readline: add stricter validation for functions called after close #58024

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

Merged
merged 1 commit into from
Apr 25, 2025

Conversation

dario-piotrowicz
Copy link
Member

@dario-piotrowicz dario-piotrowicz commented Apr 25, 2025

This reverts commit 8e7f32f (PR #57680) since the PR is introducing an unexpected issue in the REPL, see: #58014 (comment)

Fixes #58009


Thanks a lot @lpinca for spotting the problem 🙏

Once again I'm super sorry for the inconvenience here, I'm really surprised that such an issue didn't cause any test failures 😓

I'm try to reintroduce the changes in #57680 later making sure not to break the REPL 🙇

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. readline Issues and PRs related to the built-in readline module. labels Apr 25, 2025
@richardlau richardlau added dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v23.x PRs that should not land on the v23.x-staging branch and should not be released in v23.x. dont-land-on-v24.x PRs that should not land on the v18.x-staging branch and should not be released in v24.x. request-ci Add this label to start a Jenkins CI on a PR. labels Apr 25, 2025
@BridgeAR
Copy link
Member

BridgeAR commented Apr 25, 2025

Should we not try to address the shown issue instead?
I have the feeling the failures here are exactly what should be achieved?

[Edit] I see that the validations should be reintroduced later again. I guess that's also fine if it takes too long to fix the issues.

@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Apr 25, 2025
@nodejs-github-bot
Copy link
Collaborator

@lpinca
Copy link
Member

lpinca commented Apr 25, 2025

[Edit] I see that the validations should be reintroduced later again. I guess that's also fine if it takes too long to fix the issues.

Yes, the added benefit is the immediate "fix" of the flaky test (#58009).

Copy link

codecov bot commented Apr 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.27%. Comparing base (b665127) to head (2f84449).
Report is 7 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #58024   +/-   ##
=======================================
  Coverage   90.27%   90.27%           
=======================================
  Files         630      630           
  Lines      186158   186149    -9     
  Branches    36475    36477    +2     
=======================================
+ Hits       168047   168054    +7     
+ Misses      10980    10978    -2     
+ Partials     7131     7117   -14     
Files with missing lines Coverage Δ
lib/internal/readline/interface.js 96.79% <ø> (-0.02%) ⬇️

... and 26 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aduh95 aduh95 added the fast-track PRs that do not need to wait for 48 hours to land. label Apr 25, 2025
Copy link
Contributor

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

@dario-piotrowicz
Copy link
Member Author

dario-piotrowicz commented Apr 25, 2025

Should we not try to address the shown issue instead?

I'm very happy to look into the underlying issue (and I will) however unfortunately I'm visiting family for easter (I'm back home early next week) so I currently don't have as much time as I'd otherwise have to look into this promptly 🥲

So instead of keeping the bug around and cause issues maybe it'd be safer/quicker to just revert the change
(if this is not too urgent and there's time to breathe I'm happy not to revert the change)

I have the feeling the failures here are exactly what should be achieved?

Not really, the issue here is that this is breaking valid usage of the REPL 😓 (see #58014 (comment))

[Edit] I see that the validations should be reintroduced later again. I guess that's also fine if it takes too long to fix the issues.

Again I feel like this might be the most convenient solution but I am happy to proceed in any way people feel it's more appropriate here 🙂 (and again I'm very sorry for the inconvenience 🙇😢)

@aduh95 aduh95 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 Apr 25, 2025
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Apr 25, 2025
@nodejs-github-bot nodejs-github-bot merged commit b673c69 into nodejs:main Apr 25, 2025
97 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in b673c69

@dario-piotrowicz dario-piotrowicz deleted the dario/revert-57680 branch April 26, 2025 08:38
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. dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v23.x PRs that should not land on the v23.x-staging branch and should not be released in v23.x. dont-land-on-v24.x PRs that should not land on the v18.x-staging branch and should not be released in v24.x. fast-track PRs that do not need to wait for 48 hours to land. needs-ci PRs that need a full CI run. readline Issues and PRs related to the built-in readline module.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

parallel/test-repl-import-referrer is flaky
6 participants