Open matthid opened 5 years ago
@matthid any chance you could have a look at it with Process Explorer, and see if any dotnet processes hangs with "dotnet paket --version"? I've seen that quite a few times. Anyways, was just if it could narrow it down.
I see this a few times a day. Just looking at one now that has been running for 12minutes at 2.5% (on an 8 core machine). I fired up procmon, but there is no visible activity for the hanging process. I then looked at the threads in process explorer, there was only one, and it immediately woke up (which boggles my mind somewhat, correlation not causation (?)). I'm also seeing the createAppHost issue, which I can normally work my way thru by multiple incremental build swapping between Visual Studio and the command line (using dotnet build)
We have somewhat same problem here. All stuff is done and paket.exe
simply not returns. But there seems to be no activity.
I attached 2 screenshots here:
build.cmd
script (a simple batch file starting paket.exe restore
)
--> Screenshot1: ConsoleOutput.pngpaket.exe
process
--> Screenshot2: ProcessMonitor.pngAfter the CloseFile()
(Screenshot2) nothing happens, but paket.exe
in our script not returns (Screenshot1).
Additional informations:
paket.exe
is started from cmd.exe
, PowerShell
, or the new Windows Terminal
.paket.exe restore
needs to restore or not (in Screenshot1 all packages were up2date).Used environment:
paket.exe --version
: Paket version 7.2.1+8e4eb74b42fbd45f39f7afce9184c16ebb65f16cWe are a big company (but using my personal GitHub account here), developing and maintaining 1 giant .NET enterprise software product and we use paket.exe
since years now. And this is a non-critical (but annoying) problem we have, since quite a while. The paket.exe
does what it should (restore packages) and all is fine. The paket.exe
simply not returns. We "fixed"it, by using a self-written tool, that scans for a paket.exe
process and, if found, kills the process, so our script can continue then. But that´s more of a band aid patch than a solution. 😉
Any help is very appreciated!
Best regards
Nothing? Not some tip or any comment? 😞 Maybe it´s better when i open a new issue?
Description
Started a build in VS 2017 (net sdk integration):
// after some minutes
Repro steps
Not clear but there shouldn't be too many places in the code which can be responsible before
Starting full restore process
and after printing the version.This seems to happen when VSCode + Visual Studio 2017 is open and I add a new package with
paket install
and "rightclick -> build" in Visual Studio (I guess VSCode or VS is doing some paket commands behind the scenes)Expected behavior
I feel like paket is waiting for another process to exit and should tell me that. Even better would be to just work faster ;)
Actual behavior
Nothing
Known workarounds
Wait