pixi: Flaky io error on Windows

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Issue description

First off, I’m really enjoying the experience of working with pixi. I’m evaluating moving my VegaFusion project to it.

While experimenting, I’ve see a flaky issue on windows in GitHub actions. Here’s an example of the error:

Run pixi run test-py-jupyter-headless
  pixi run test-py-jupyter-headless
  shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
  × an io error occurred
  ├─▶ failed to unpack `\\?\C:
  │   \Users\runneradmin\AppData\Local\rattler\cache\pkgs\nodejs-[2](https://github.com/hex-inc/vegafusion/actions/runs/5911727817/job/16034477872#step:6:2)0.5.1-
  │   h57928b[3](https://github.com/hex-inc/vegafusion/actions/runs/5911727817/job/16034477872#step:6:3)_0\node.exe`
  ├─▶ failed to unpack `node.exe` into `\\?\C:
  │   \Users\runneradmin\AppData\Local\rattler\cache\pkgs\nodejs-20.[5](https://github.com/hex-inc/vegafusion/actions/runs/5911727817/job/16034477872#step:6:6).1-
  │   h5[7](https://github.com/hex-inc/vegafusion/actions/runs/5911727817/job/16034477872#step:6:8)92[8](https://github.com/hex-inc/vegafusion/actions/runs/5911727817/job/16034477872#step:6:9)b3_0\node.exe`
  ├─▶ request or response body error: error reading a body from connection:
  │   end of file before message length reached
  ├─▶ error reading a body from connection: end of file before message length
  │   reached
  ╰─▶ end of file before message length reached

It doesn’t happen every time (maybe 20% of the time?), and the library it fails on is different each time (it’s nodejs above).

I’m wondering if there’s something that just needs some retry logic.

Thanks!