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
Lock dir not cleaned on compromised lock & fatal error lock is already released #5324
Comments
How this is happening in the real world?
CLI reports all thrown exceptions to |
it occurred to me when |
@highalps At what point in your build does it happen and what is the cpu but especially the io usage at that time? (a playback of nuxt build with top & iotop would be preferred) I am having difficulties to reproduce the compromised lock behaviour consistently in the real world. It might be that the locking we implemented is too stringent, but before we can decide on how to proceed we need to know exactly when and why the lock gets compromised. And preferable we need to be able to reproduce that behaviour. Any help would be appreciated. |
This also happened to us (Nuxt 2.5.1 with Typescript). I managed to circumvent the issue by deleting the node_modules, reinstalling all packages and building fresh. A lock file was not deleted in the |
I have this error as well. I have deleted node_modules, updated all packages etc. Following. |
For people here, see my comment here about possible causes: #5331 (comment) Bottom line is, if you are using Node v9 then upgrade to v10 (which is a lts release and had major performance improvements). If you are already on v10+, we still dont understand yet why the lock gets compromised so often in some environments. |
|
Have recently got this after upgrading to 2.5.1. Using yarn. I'm receiving it on a docker image with node 10.7.0 running on bitbucket pipelines, build time is 77.23s. OS is ubuntu 16. Working fine for me locally on Mac, node 10.7.0, with a build time of 167.98s. Exact same code. Downloading entire node_modules folder each time. Weird thing is if I mount myself in the container i'm using in pipelines locally, it works fine also 🤔🤔 |
Yesterday I noticed an issue where the lock was compromised due to a small difference in the mtime that was set on the lock file with |
I am also facing this issue. My prod builds are failing after installing packages. Is there any solution available? |
@shivgarg5676 As previously mentioned, use |
but we are using v2.4.5 |
Lock support was only added to Nuxt in |
Changing nuxt version from 2.5.1 to 2.4.5 made the problem disappear here. @pimlie |
upgrade from nodejs v8 to v10 resolved the issue, thx @pimlie |
I'm also change my package.json from |
It's also happening to me, after upgrade from v2.4.5 to v2.5.1.
but, with this setup, the CI will fails in
to solve this, you can see in above config, i need to make the cache folder writeable..
then, I was here. So, basically the solution is to add |
@nmfzone The same situation with u. |
It worked |
@pimlie Looks nice, after upgrading to Node v10.15.3. I think it's time to upgrade too. 👍 |
@pimlie But, It seems like breaking changes for Nuxt 2.5.x. Since Nuxt < 2.5 work in Node < 10 and Nuxt >= 2.5 will not work in Node < 10 (if they're not used I think |
@nmfzone It was a bug (or actually 2 bugs), not a feature. Using
|
Problem fixed with
|
These issues should be fixed in |
Version
v2.5.1
Reproduction link
https://github.com/nuxt/nuxt.js
Steps to reproduce
touch -t 200012311800 ./node_modules/.cache/nuxt/build-lock-*.lock
Unable to update lock
warning to be displayedWhat is expected ?
Only the warning should be displayed. Not sure why the trace is showing, probably consola feature?
What is actually happening?
./node_modules/.cache/nuxt
folder still contains the.lock
folder (the other folder is removed)Additional comments?
Will have a look at this, creating this issue for reference
The text was updated successfully, but these errors were encountered: