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

fix(ext/node): don't throw error for unsupported signal binding on windows #25699

Merged
merged 3 commits into from
Sep 19, 2024

Conversation

kt3k
Copy link
Member

@kt3k kt3k commented Sep 18, 2024

This PR changes the handling of unsupported signals on windows. Currently it throws an error if process.on is called with unsupported signal (ex. SIGHUP) on windows. That causes #25675 for example.

This PR changes it to not throw the error instead let it only print the warning messages.

closes #25675

@kt3k kt3k added the ci-draft Run the CI on draft PRs. label Sep 18, 2024
@kt3k kt3k marked this pull request as ready for review September 18, 2024 06:25
Copy link
Member

@littledivy littledivy left a comment

Choose a reason for hiding this comment

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

LGTM

@kt3k kt3k merged commit f460188 into denoland:main Sep 19, 2024
33 checks passed
@kt3k kt3k deleted the fix-unsupported-signal-on-windows branch September 19, 2024 03:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-draft Run the CI on draft PRs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

puppeteer.launch() throws at process.on("SIGHUP") call on windows
2 participants