[Bug?]: Random ESOCKETTIMEDOUT's on @mui/[email protected]

[Trojaner]

Self-service

• [ ] I'd be willing to implement a fix

Describe the bug

On our docker-based CI builds @mui/[email protected] randomly fails to install for some reason. Is it possible that our server IP or subnet is blocked by the yarn registry?

To reproduce

Note: I cannot reproduce it locally. Only on the server.

yarn init -2 yarn add @mui/[email protected]

Environment

System:
    OS: Linux 6.8 Alpine Linux
    CPU: (8) x64 AMD EPYC 7282 16-Core Processor
  Binaries:
    Node: 21.7.1 - /tmp/xfs-41332753/node
    Yarn: 4.4.1 - /tmp/xfs-41332753/yarn
    npm: 10.5.0 - /usr/local/bin/npm

Additional context

44.86 [2/4] Fetching packages... 78.41 info There appears to be trouble with your network connection. Retrying... 111.6 info There appears to be trouble with your network connection. Retrying... 144.7 info There appears to be trouble with your network connection. Retrying... 204.0 info There appears to be trouble with your network connection. Retrying... 239.8 error An unexpected error occurred: "https://registry.yarnpkg.com/@mui/icons-material/-/icons-material-5.16.7.tgz: ESOCKETTIMEDOUT". 239.8 info If you think this is a bug, please open a bug report with the information provided in "/build/yarn-error.log". 239.8 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

[arcanis]

Wrong repository (this occurred on v1), and it's likely a network error on your side or your registry's side.

[sleepywei]

I have the same issue on my MacBook yarn version v1.22.22 npm: '10.7.0' node: '18.20.3'

[sleepywei]

I figured out the problem was the slow network and the packages being installed were very large. Try --network-timeout option when running yarn install