Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

EPERM: operation not permitted #35086

Closed
2 tasks done
herecydev opened this issue Mar 9, 2022 · 1 comment · Fixed by #35154
Closed
2 tasks done

EPERM: operation not permitted #35086

herecydev opened this issue Mar 9, 2022 · 1 comment · Fixed by #35154
Labels
status: confirmed Issue with steps to reproduce the bug that’s been verified by at least one reviewer. type: bug An issue or pull request relating to a bug in Gatsby

Comments

@herecydev
Copy link
Contributor

herecydev commented Mar 9, 2022

Preliminary Checks

Description

This can be replicated on multiple windows devices, although the error is random; sometimes it throws and sometimes the build is succesful. At a guess maybe 10-15% of the time we can see this.

This seems to only exhibit since 4.8.0+ so possibly related to typescript additions, looks like parcel is generating files in that area? gatsby clean is also not helping

Untitled

Reproduction Link

https://github.com/gatsbyjs/gatsby

Steps to Reproduce

  1. gatsby build

Expected Result

Does not fail

Actual Result

Fails

Environment

System:
    OS: Windows 10 10.0.19042
    CPU: (16) x64 AMD Ryzen 9 5950X 16-Core Processor            
  Binaries:
    Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 3.1.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (98.0.1108.55)
  npmPackages:
    gatsby: ^4.9.2 => 4.9.2 
    gatsby-cypress: 2.9.0 => 2.9.0 
    gatsby-plugin-google-tagmanager: ^4.9.0 => 4.9.0 
    gatsby-plugin-image: ^2.9.0 => 2.9.0 
    gatsby-plugin-newrelic: ^2.2.2 => 2.2.2 
    gatsby-plugin-react-helmet: ^5.9.0 => 5.9.0 
    gatsby-plugin-remove-generator: ^1.2.0 => 1.2.0 
    gatsby-plugin-sharp: ^4.9.0 => 4.9.0 
    gatsby-plugin-sitemap: ^5.9.0 => 5.9.0 
    gatsby-plugin-styled-components: ^5.9.0 => 5.9.0 
    gatsby-plugin-webpack-bundle-analyser-v2: 1.1.26 => 1.1.26 
    gatsby-source-filesystem: ^4.9.0 => 4.9.0 
    gatsby-transformer-remark: ^5.9.0 => 5.9.0 
    gatsby-transformer-sharp: ^4.9.0 => 4.9.0 
  npmGlobalPackages:
    gatsby-cli: 4.5.2

Config Flags

PARALLEL_SOURCING: true,
PRESERVE_FILE_DOWNLOAD_CACHE: true,

@herecydev herecydev added the type: bug An issue or pull request relating to a bug in Gatsby label Mar 9, 2022
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Mar 9, 2022
@provalinf

This comment was marked as duplicate.

@wardpeet wardpeet added status: confirmed Issue with steps to reproduce the bug that’s been verified by at least one reviewer. status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Mar 17, 2022
@LekoArts LekoArts removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Mar 17, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
status: confirmed Issue with steps to reproduce the bug that’s been verified by at least one reviewer. type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants