Domantas Petrauskas

Any updates on this? Maybe somebody came up with a workaround? Currently dealing with this on https://github.com/ptrdom/scalajs-esbuild/actions/runs/6113494804/job/16593092828?pr=12.

Hmm, that is quite a problem then. I know this is more of a github runners issue, things are getting broken on them from time to time, but it might...

All is good on my Windows Desktop too. Now I started to remember some things - I had this issue some years ago with Windows GitHub runners, issue was that...

I could try testing this out on my repo where I am having this issue, though releasing a snapshot sbt version somewhere for the runner to use is a bit...

This is also quite difficult to replicate, because the issue is specific to how GitHub sets up its runners, so not possible to replicate locally, and the range is not...

I think it is a problem of Coursier, but my guess is that it is resource intensive enough on the Coursier side to fix so that it would be simpler...

> > Ideally if `port` is set to `0` then this would just be passed to Go `listen` implementation and it would pick a free random port. > > I'm...

Could also be a problem with launcher - it does extract the arguments that are then passed to sbt.

So apparently `=` is a default delimiter in batch scripts, workarounds for this issue seem to be present for certain types of arguments in launcher script already. I am starting...

I can see how this is useful, and it should be quite easy to implement. I think we can proceed with it if we keep it as simple as possible...