Replies: 2 comments 1 reply
-
@JasonGore Sorry for delay, still valid? |
Beta Was this translation helpful? Give feedback.
0 replies
-
We still see the issue occasionally in our CI but not as frequently as when I created this conversation item. I'd still be curious to see if there's any insight into if and how state could cross processes, whether via cross-process cache, file I/O, or other. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I work on a large scale project where webpack runs in CI hundreds of times per day. For the last few weeks, we are seeing an intermittent but persistent rate (~1%) of "Module parse failed" errors with unterminated strings, regular expressions, and unexpected input. In all cases, the parsed input doesn't match what's actually on disk. In some cases parsed input seems truncated while in others parsed input has appended content. Actual file contents on disk seem valid in all cases, and don't change between successful and unsuccessful runs.
This seems completely unrelated to obvious loader config issues that would lead to consistently reproducible failures. It happens with completely different webpack loader configs and there seem to be no common loaders involved. I don't think it could be a broad issue with file I/O or handles as we run a wide variety of processes and build tasks and none fail with similar file I/O issues. As a result, this seems to be some sort of Node or webpack architectural issue. It seems like there is some type of pollution or corruption of global state or file streams that's causing these intermittent types of errors. I wanted to post here in case anyone has ever encountered anything remotely similar as it's been a real head scratcher for us.
We do have many bundles running in parallel on these VMs in CI, but they are running in their own webpack CLI-invoked Node processes and should be isolated from each other. I'm curious if anybody knows of any way that state could somehow pollute across bundles happening in separate processes.
I could also use any help trying to pinpoint the issue more closely, such as tracing loader chain activity, printing file contents/stats, tracing parsed input, etc.
webpack: 5.82.0, 5.88.2
Node: v18.17.1
OS: Ubuntu 22.04.2 LTS
Beta Was this translation helpful? Give feedback.
All reactions