I'm having a critical error "EPERM: operation not ...
# cy10-feedback
s
I'm having a critical error "EPERM: operation not permitted, watch `path\to\project\.git\index.lock`". It suddenly occurs, I was reading some testing example files (e.g. assertions.cy.js) and the test runner closes. It happened 4 times since I upgraded. Full details: Couple of hours ago, I upgraded from 9.7.0 by doing
npm install --save-dev cypress@10.0.0
. All went good. The wizard changed my files and whatnot. Everything worked as intended and suddenly the test runner crashed on every time I opened it (via
cypress open
). (The terminal output is bad formatted, it always happens) My machine: Windows 10 21H2 19044.1706 NodeJS v. 16.15.0 NextJS 12.1.6
I rerun cypress. By the way, what is that long GET request? It says something about "error"
Copy code
GET /v4/threatListUpdates:fetch?$req=Ch0KDGdvb2dsZWNocm9tZRINMTAyLjAuNTAwNS42MxopCAUQARobCg0IBRAGGAEiAzAwMTABEIDxDRoCGAm9ya0EIgQgASACKAEaKQgBEAEaGwoNCAEQBhgBIgMwMDEwARDp4AoaAhgJ9KuyBiIEIAEgAigBGikIBxABGhsKDQgHEAYYASIDMDAxMAEQpqULGgIYCQMcDOciBCABIAIoARonCAEQARoZCg0IARAGGAEiAzAwMTADEBQaAhgJzF08RSIEIAEgAigDGigIARAIGhoKDQgBEAgYASIDMDAxMAQQtCgaAhgJ4UTeLCIEIAEgAigEGigIDxABGhoKDQgPEAYYASIDMDAxMAEQ4nEaAhgJhHpagyIEIAEgAigBGicIChAIGhkKDQgKEAgYASIDMDAxMAEQBxoCGAns9SCMIgQgASACKAEaJwgJEAEaGQoNCAkQBhgBIgMwMDEwARAgGgIYCXdLtx4iBCABIAIoARooCAgQARoaCg0ICBAGGAEiAzAwMTABENcPGgIYCXeQeGIiBCABIAIoARopCA0QARobCg0IDRAGGAEiAzAwMTABEJW9ARoCGAm3eXEYIgQgASACKAEaKQgDEAEaGwoNCAMQBhgBIgMwMDEwARCpsgoaAhgJmKL9ASIEIAEgAigBGikIDhABGhsKDQgOEAYYASIDMDAxMAEQ6bgGGgIYCVET_t4iBCABIAIoARooCBAQARoaCg0IEBAGGAEiAzAwMTABEI4SGgIYCe4qxDIiBCABIAIoASICCAE=&$ct=application/x-protobuf&key=AIzaSyBOti4mM-6x9WDnZIjIeyEU21OpBXqWBgw 200 755.274 ms - -
[514256:0601/171254.802:ERROR:gpu_init.cc(446)] Passthrough is not supported, GL is disabled, ANGLE is
c
Hey @swift-angle-95455, thanks for trying out Cypress 10. Your EPERM error is known and will be fixed in a patch release later today, so look out for that: https://github.com/cypress-io/cypress/pull/22011
That long GET request is from Chrome, Chrome is doing some internal requests to update the malware detection metadata.
15 Views