-
Notifications
You must be signed in to change notification settings - Fork 800
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
lstat error when use yarn to install nodejs package #3158
Comments
I'm having the same issue since the April update, it happens for one project though. The rest of my projects use I tried the same project on other machine and it also fails, it fails specifically when running jest tests. Happens on both node 9.8 and 10. Yarn version is 1.6.0 |
Same issue here after the april update. Tried with yarn 1.3, 1.5 and 1.6, and in two different projects. Also tried with yarn installed as a windows binary as well as installed inside wsl. Error from project 1: Error from project 2: |
@therealkenc repro steps on build 1803 are as following
|
The problem is almost 100% reproducible with watchman git hook running. Visit a few large git repositories, run |
Yet another victim of #2937 I recommend using LxFs folders (/home/*) when possible since is the most Linux-like file system. |
Thanks. That makes sense. |
I was struggling with this problem in |
Go with a new one. There was no repro in the OP so we can't even be sure @onomatopellan's theory is correct. |
❯ cat /etc/wsl.conf
[automount]
enabled = true
root = /
options = "metadata,umask=22,fmask=11,case=off" ❯ mount -l
rootfs on / type lxfs (rw,noatime)
root on /root type lxfs (rw,noatime)
home on /home type lxfs (rw,noatime)
data on /data type lxfs (rw,noatime)
cache on /cache type lxfs (rw,noatime)
mnt on /mnt type lxfs (rw,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
none on /dev type tmpfs (rw,noatime,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,gid=5,mode=620)
none on /run type tmpfs (rw,nosuid,noexec,noatime,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime)
none on /run/shm type tmpfs (rw,nosuid,nodev,noatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noatime)
C: on /mnt/c type drvfs (rw,noatime,uid=1000,gid=1000,umask=22,fmask=11,metadata,case=off)
D: on /d type drvfs (rw,noatime,uid=1000,gid=1000,umask=22,fmask=11,metadata,case=off)
F: on /f type drvfs (rw,noatime,uid=1000,gid=1000,umask=22,fmask=11,metadata,case=off)
G: on /g type drvfs (rw,noatime,uid=1000,gid=1000,umask=22,fmask=11,metadata,case=off)
I: on /i type drvfs (rw,noatime,uid=1000,gid=1000,umask=22,fmask=11,metadata,case=off) Still getting errors when using yarn: |
@Fumler I can't repo that. My yarn cache is on a Lxfs folder Also I delete any project folder and create it again after using case=off option. edit:fixed misunderstanding |
Thank you @onomatopellan ! Putting yarn cache location on a Lxfs folder fixed the issue. |
Still get errors reported by @Fumler OS Name Microsoft Windows 10 Pro Video: |
@yshterev Are you sure your D:\workspace is a brand new folder created after enabling case=off? |
@onomatopellan All folders say |
It won't be case related if "Different files reported missing every time it does not work". The problem would be more deterministic. Will hold open for a bit until the #2712 hypothesis is confirmed. Which sounds plausible, but I already jumped the gun once on this one. Try 17655 or better and if the problem goes away we'll put it to bed. |
Not working, my wsl.conf is correct:
Yet I get random error with jest so WSL is unusable for me... |
Hi, I think I found something similar to this problem. I was dabbling with a piece of code which list files in a specified directory recursively using I've made a simple NPM package, async-dirtree-test, to test this problem and I found that it is likely to fail while handling a directory which has many child directories, like
|
If you can get your test case to fail on 17760, then your repro is probably worthy of rebooting into a new issue. Your fail looks to be on LxFS as well, while this issue wandered into the case sensitivity flag on DrvFS. You'll need (a) repro steps from a clean install (most of which you will personally find "obvious") that can be cut and pasted and (b) link to an strace log.
As well, those repro steps are going need to include steps to populate "the directory" that has many child directories not "a directory" that has many child directories (or build the tree in the test code). Also some indications on what "likely" means. "Will fail" is what you are shooting for here, because if someone cuts-and-pastes your repro steps and it doesn't fail, the new issue will go dark pretty quick. Loop the test if you have to. It's a good effort, so thanks for that. It unfortunately makes for a less than ideal test case, because while the code is short there are a lot of big moving pieces (nodejs, V8, libuv). But it's more likely than not you're onto something. |
@therealkenc, Preparing Sample Directory for Testing
Thank you very much for your tips. At the moment, I don't know how big exactly the directory tree should be to trigger the failure. I'm trying this on a directory, 10 out of 10 invocations of the sample program on
Here is the result of
I've also tried this on AvaKathrynShaw/React-16-Demo which can be prepared with these commands:
5 out of 5 invocations of the sample program on it have failed on my machine. Here is the result:
More Things and
|
|
UPD: seems to be fixed in 1809 |
This one lacks any actionable repro let alone declaration of fixeedness. Closing on the basis that we'll probably never know the cause of the OP |
Your Windows build number: windows 10 1803
What you're doing and what's happening:
When i use yarn to install nodejs package, it will cause error with
lstat
.What's wrong / what should be happening instead:
Error Logs:
The text was updated successfully, but these errors were encountered: