Skip to content

Fix Windows malicious file analysis waiting problem - #398

Merged
aduh95 merged 7 commits into
nodejs:mainfrom
ngnlTeto:fix-enoent-windows
Feb 27, 2024
Merged

Fix Windows malicious file analysis waiting problem#398
aduh95 merged 7 commits into
nodejs:mainfrom
ngnlTeto:fix-enoent-windows

Conversation

@ngnlTeto

Copy link
Copy Markdown
Contributor

Fixes#246

That should fix the problem that windows malicious file analysis blocks the freshly downloaded file.
I couldn't reproduce the error on my side currently, but it should help.

@ngnlTeto

Copy link
Copy Markdown
ContributorAuthor

I was able to reproduce it and verify that it fixed the error.

Comment threadsources/corepackUtils.ts Outdated
Comment threadsources/corepackUtils.ts Outdated
Comment threadsources/corepackUtils.ts Outdated
Comment threadsources/corepackUtils.ts Outdated
Comment threadsources/corepackUtils.ts Outdated

@aduh95aduh95 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I don't have a Windows machine to confirm if it solves the issue, but the code LGTM

@aduh95
aduh95 enabled auto-merge (squash) February 27, 2024 09:07
@aduh95
aduh95 merged commit 295a1cd into nodejs:mainFeb 27, 2024
@github-actionsgithub-actionsBot mentioned this pull request Feb 23, 2024
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

corepack preapre : ENOENT: no such file or directory, stat

4 participants

@ngnlTeto@styfle@merceyz@aduh95