Skip to content
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

Unexpected (and very bad) data loss #1224

Closed
theodoreb opened this issue Oct 19, 2016 · 2 comments
Closed

Unexpected (and very bad) data loss #1224

theodoreb opened this issue Oct 19, 2016 · 2 comments

Comments

@theodoreb
Copy link

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
I run yarn in my project folder and it tries to delete everything from the parent directory. See console output:

theodore@monkey:~/DEV/PERSO/PEP$ yarn
yarn install v0.15.1
info No lockfile found.
[1/4] Resolving packages...
warning intern > istanbul > fileset > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[2/4] Fetching packages...
[3/4] Linking dependencies...
error EACCES: permission denied, unlink '~/DEV/PERSO/pwa/docroot/sites/default/default.settings.php'
    at Error (native)
info Visit http://yarnpkg.com/en/docs/cli/install for documentation about this command.

Tried with latest yarn version, same thing.

If the current behavior is a bug, please provide the steps to reproduce.

  1. Checkout the PEP repository: https://github.com/jquery/PEP
  2. Run yarn
  3. Watch your parent folder get deleted.

What is the expected behavior?
My data is not deleted.

Please mention your node.js, yarn and operating system version.
See redacted yarn-error.txt.

@sevenseacat
Copy link

Verified with the PEP repository on Yarn v0.16.1, and node v6.9.1. All contents of the parent folder (files and folders) deleted. npm install doesn't have the same behaviour.

However, I've done the same thing with other projects and this bug hasn't happened...

@chlunde
Copy link
Contributor

chlunde commented Oct 26, 2016

Looks like it was fixed by #1441

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants