"Restoring packages..." hangs

[UweKeim]

Out of the blue, in one of my projects, cs-script (4.13.0.0) hangs:

C:\Users\ukeim>css -nuget:restore "c:\P\zeta-uploader-main\Core\Source\do-build-all.cs"
Restoring packages...
   -force:3600 ZetaFileSync.PublicRuntime
   morelinq
   Newtonsoft.Json
   QuickUploader.WebApiAccessor
   RestSharp
   SharpZipLib
   ZetaDeployer.RuntimeUploader
   ZetaShortPaths

I cancelled after approx. 10 minutes.

Is there any way to look for logs or can I turn on a verbose mode to see what's going on?

[UweKeim]

OpenAI Codex suggested me to do this:

set NuGetAudit=false

And then try again. In fact, it passes the stalling and continues and finally finishes successfully:

C:\Users\ukeim>set NuGetAudit=false

C:\Users\ukeim>css -nuget:restore "c:\P\zeta-uploader-main\Core\Source\do-build-all.cs"
Restoring packages...
   -force:3600 ZetaFileSync.PublicRuntime
   morelinq
   Newtonsoft.Json
   QuickUploader.WebApiAccessor
   RestSharp
   SharpZipLib
   ZetaDeployer.RuntimeUploader
   ZetaShortPaths
Mapping packages to assemblies...
Compile: OK

---

Some more things Codex suggests:

• Most likely root cause of the “hang”: css spawns dotnet publish and does not drain stdout/stderr quickly enough. Once dotnet emits enough output (often >~4KB of warnings), its stdout buffer fills up, dotnet blocks, and css waits forever. This can start “recently” because newer .NET/NuGet versions can emit more warnings (e.g. vulnerability/audit output).

• Workaround (usually immediate): reduce warning output before running css.

  • Minimal (disable NuGet audit output):
    • PowerShell: $env:NuGetAudit='false'
    • CMD: set NuGetAudit=false
  • “Sledgehammer” (suppress specific NuGet warnings so output stays small):
    • PowerShell: $env:NoWarn='NU1603;NU1701;NU1904'
    • CMD: set NoWarn=NU1603;NU1701;NU1904
  • Then retry: css -nuget:restore "c:\P\zeta-uploader-main\Core\Source\do-build-all.cs"

[oleg-shilo]

Very interesting...

I think you are spot on. It was a risky implementation of the dotnet.execution when ReadToEnd was called after the WaitForExit.

I have changed it and it should not block even if the stdout buffer overflow.
I have also introduced a timeout that can be overwritten via envar
So the output will print a clear message if the restoring hangs:

[UweKeim]

Thank you so much, Oleg!

[oleg-shilo]

Done. Released.
You can now update from teh Nuget
https://github.com/oleg-shilo/cs-script/releases/tag/v4.13.1.0