Fabrizio Ferrai

I think the PR is sound, CI currently fails presumably because of the Azure debacle

We'll need #4548 merged before this can pass

@kritzcreek I know that commit was 7y ago, but do you have any recollection about this?

The 0.21.x line is the legacy codebase, which is not maintained anymore. Would you be able to give this a try with `spago@next`?

Good to know that the new spago works! It's not alpha in the sense that "things are changing all the time" anymore, but more like "it still has paper cuts...

That said, I'll close this ticket as it doesn't affect the new spago (which is now living in this repo)

I'll reopen this since it seems to be a recurring issue - we should try to find a way to replicate this in CI so we can issue a reasonable...

We are using Node 22 in CI: https://github.com/purescript/spago/blob/b13857dcae4c908af20f5ad010b2581f6a4bab75/.github/workflows/build.yml#L38-L41 So I wonder if there's something else at play here?

Agreed, we should expose this with a flag. `OnlineBypassCache` was recently added (together with the `registry transfer` command), so we didn't get around to exposing this yet.

I see. We are using [execa](https://github.com/JordanMartinez/purescript-node-execa) for spawning processes, and I suspect that the TTY behaviour was lost in the translation from Haskell. All in all this sounds like a...