[Bug?]: UV causing EBADF errors on Android during yarn install

[FossPrime]

Self-service

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

Describe the bug

UV causing EBADF errors on Android. Possibly Azure AppService as well. Seems to be an issue code-server users are also encountering. Using NPM instead works perfectly.

➤ YN0001: │ Error: yargs@npm:13.3.2: EBADF: bad file descriptor, copyfile '/data/data/com.termux/files/home/.yarn/berry/cache/yargs-npm-13.3.2-1588f5dd4c-7.zip' -> '/data/data/com.termux/files/usr/tmp/xfs-4793c4c3/yargs-npm-13.3.2-1588f5dd4c-7.zip'  ➤ YN0001: │ Error: yargs@npm:16.2.0: EBADF: bad file descriptor, copyfile '/data/data/com.termux/files/home/.yarn/berry/cache/yargs-npm-16.2.0-547873d425-7.zip' -> '/data/data/com.termux/files/usr/tmp/xfs-581a5ccd/yargs-npm-16.2.0-547873d425-7.zip'  ➤ YN0001: │ Error: yargs@npm:14.2.3: EBADF: bad file descriptor, copyfile '/data/data/com.termux/files/home/.yarn/berry/cache/yargs-npm-14.2.3-b84ca3cee2-7.zip' -> '/data/data/com.termux/files/usr/tmp/xfs-79c6d10a/yargs-npm-14.2.3-b84ca3cee2-7.zip'  ➤ YN0001: │ Error: yeast@npm:0.1.2: EBADF: bad file descriptor, copyfile '/data/data/com.termux/files/home/.yarn/berry/cache/yeast-npm-0.1.2-19a347595d-7.zip' -> '/data/data/com.termux/files/usr/tmp/xfs-25e98209/yeast-npm-0.1.2-19a347595d-7.zip'     ➤ YN0001: │ Error: yorkie@npm:2.0.0: EBADF: bad file descriptor, copyfile '/data/data/com.termux/files/home/.yarn/berry/cache/yorkie-npm-2.0.0-90a2c44491-7.zip' -> '/data/data/com.termux/files/usr/tmp/xfs-4be4d46d/yorkie-npm-2.0.0-90a2c44491-7.zip'  ➤ YN0000: └ Completed in 4s 535ms
➤ YN0000: Failed with errors in 21s 835ms

To reproduce

1. Install yarn on Android or ChromeOS with Android (easiest way is Termux from F-Droid app store)
2. Run yarn on a large project like Vue

Environment

System:                                                                                                                        
  OS: android                                                                                                                  
  CPU: Unknown
Binaries:                                                                                                                      
  Node: 16.13.2 - /data/data/com.termux/files/usr/tmp/xfs-a915398e/node                                                        
  Yarn: 2.4.3 - /data/data/com.termux/files/usr/tmp/xfs-a915398e/yarn                                                          
  npm: 8.1.2 - /data/data/com.termux/files/usr/bin/npm

Additional context

No response

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

[FossPrime]

This cannot be reproduced in Sherlock as this is an OS specific issue, please add upholded