search

fsprojects / Paket

A dependency manager for .NET with support for NuGet packages and Git repositories.
https://fsprojects.github.io/Paket/
MIT License
2.02k stars 520 forks source link

Paket retry on paket.locked almost works #3321

Open matthid opened 6 years ago

matthid commented 6 years ago

Description


  Could not acquire lock to C:\proj\{Project}\source\Server.WindowsService\obj\paket.locked.
  Access to the path 'C:\proj\{Project}\source\Server.WindowsService\obj\paket.locked' is denied.
  Trials left: 99.
  Could not acquire lock to C:\proj\{Project}\source\Server.WindowsService\obj\paket.locked.
  Access to the path 'C:\proj\{Project}\source\Server.WindowsService\obj\paket.locked' is denied.
  Trials left: 98.
  Could not acquire lock to C:\proj\{Project}\source\Server.WindowsService\obj\paket.locked.
  Access to the path 'C:\proj\{Project}\source\Server.WindowsService\obj\paket.locked' is denied.
...
...
  Could not acquire lock to C:\proj\{Project}\source\Server\obj\paket.locked.
  Access to the path 'C:\proj\{Project}\source\Server\obj\paket.locked' is denied.
  Trials left: 1.

  Process is terminated due to StackOverflowException.

Expected behavior

Fail with a reasonable error instead of Stack-Overflow.

Actual behavior

Fails with a StackOverflowException.

forki commented 6 years ago

Please send help 😣

Matthias Dittrich notifications@github.com schrieb am Mi., 1. Aug. 2018, 16:18:

Reopened #3321 https://github.com/fsprojects/Paket/issues/3321.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fsprojects/Paket/issues/3321#event-1765347887, or mute the thread https://github.com/notifications/unsubscribe-auth/AADgNFqYtbkEFmF2owOSQ7P85K-x4-WFks5uMbi5gaJpZM4Vqlfu .

dlidstrom commented 5 years ago

I saw this happening when the obj folder was locked somehow, after I tried to delete the folder it was left in place but without any permissions on it. When I closed VS Code the folder was finally deleted and I could run dotnet publish -c Release again.