-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Build Tooling: Watch task can produce error when many files change (ENAMETOOLONG) #14960
Labels
Good First Issue
An issue that's suitable for someone looking to contribute for the first time
Needs Dev
Ready for, and needs developer efforts
[Type] Bug
An existing feature does not function as intended
[Type] Build Tooling
Issues or PRs related to build tooling
Comments
aduth
added
[Type] Bug
An existing feature does not function as intended
[Type] Build Tooling
Issues or PRs related to build tooling
labels
Apr 12, 2019
I've seen this error too:
|
gziolo
added
Good First Issue
An issue that's suitable for someone looking to contribute for the first time
Needs Dev
Ready for, and needs developer efforts
labels
Apr 23, 2019
It's definitely this error I'm always running into. Every time I change branches, |
I'll plan to work on this on Friday. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Good First Issue
An issue that's suitable for someone looking to contribute for the first time
Needs Dev
Ready for, and needs developer efforts
[Type] Bug
An existing feature does not function as intended
[Type] Build Tooling
Issues or PRs related to build tooling
Recently I've observed that in changing branches, the process which runs
npm run dev
will halt with an error:I expect the issue here is that we group many file updates into a single rebuild which is run after a 100ms delay:
gutenberg/bin/packages/watch.js
Lines 67 to 75 in aac1a37
For some reason, this appears to be used in the build step when creating the target directory for the built file:
gutenberg/bin/packages/build.js
Line 169 in aac1a37
I would expect this should only be using an individual file's directory, not the full set of changed files. It's unclear to me why it does, or if there are other ramifications to the fact that
buildJsFileFor
might be receiving afile
argument of multiple files.The text was updated successfully, but these errors were encountered: