[Bug?]: Shrelock Playground gets stuck at "checking the repo" state with errors in Console

[trivikr]

Self-service

• I'd be willing to implement a fix

Describe the bug

Shrelock Playground gets stuck at "checking the repo" state with errors in Console

To reproduce

Visit Sherlock Playground at https://viko0.sse.codesandbox.io/
Notice that several fetch and 404 errors are thrown when page loads.

Add an example code for repro, and press run:

await packageJsonAndInstall({
  "name": "test-yarn-version",
  "packageManager": "[email protected]"
});

await expect(yarn(`--version`)).resolves.toBe("1.12.19");

Notice that CORS error is thrown in Console:

Access to fetch at 'https://viko0.sse.codesandbox.io/api/check-repo' from origin 'https://yarnpkg.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Screenshot

Environment

  System:
    OS: macOS 12.1
    CPU: (8) arm64 Apple M1 Pro
  Browsers:
    Brave Browser: 104.1.42.88
    Safari: 15.2

Additional context

No response

[yarnbot]

This issue reproduces on master:

Error: expect(received).resolves.toBe(expected) // Object.is equality

Expected: "1.12.19"
Received: "4.0.0-rc.18.dev
"
    at Object.toBe (/github/workspace/.yarn/cache/expect-npm-24.8.0-8c7640c562-44ff9ab1e7.zip/node_modules/expect/build/index.js:202:20)
    at module.exports (evalmachine.<anonymous>:7:42)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async /github/workspace/.yarn/cache/@arcanis-sherlock-npm-2.0.3-558f52b79f-286d94b96d.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:57:13
    at async executeInTempDirectory (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-2.0.3-558f52b79f-286d94b96d.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:18:16)
    at async executeRepro (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-2.0.3-558f52b79f-286d94b96d.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:25:12)
    at async ExecCommand.execute (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-2.0.3-558f52b79f-286d94b96d.zip/node_modules/@arcanis/sherlock/lib/commands/exec.js:26:38)
    at async ExecCommand.validateAndExecute (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-4061026d74.zip/node_modules/clipanion/lib/advanced/Command.js:161:26)
    at async Cli.run (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-4061026d74.zip/node_modules/clipanion/lib/advanced/Cli.js:74:24)
    at async Cli.runExit (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-4061026d74.zip/node_modules/clipanion/lib/advanced/Cli.js:83:28)

[trivikr]

Sherlock Playground now has more issues.

It times out in most cases.

Screenshot

Other times, it returns 502 Bad Gateway error

Screenshot

In some cases when it loads, it returns ENOSPC: no space left on device error

Screenshot

[RDIL]

We're aware and trying to resolve the matter. We think the issue might be on the CodeSandbox side of things, so we're in contact with the folks who run it. Sorry about the issue in the meantime.

[paul-soporan]

The Bad Gateway due to ENOSPC is because the Next cache doesn't get cleared when the server restarts. I need to look into making server restarts clear it, but for now I cleared it manually It's actually due to the fact that the cloned repo doesn't get pruned, it takes up a lot more space than the Next cache.

I haven't looked into fixing the original CORS error yet.

[trivikr]

Verified that no CORS errors are thrown in Console on Sherlock Playground.

[trivikr]

The CORS errors are now thrown during "running the repro" state.

I've created a new bug report at #4855