-
Notifications
You must be signed in to change notification settings - Fork 710
On Windows, cabal hangs indefinitely when fetching a git
source-repository-package
#8688
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank you for the report. Could this be a Also, are we sure the same works fine on, say, Linux? Is there a test in CI for exactly this case (e.g., skipped on Windows, because we though it's a CI fluke)? |
@Mikolaj I was able to build the same package under WSL, so I believe it does work in Linux, though of course there could be some confounding variable. Looks when I built from source, cabal used process 1.6.15.0, which is one version older than the newest version on hackage. I can check later today if a small program that just waits for a git process has the same issue on my machine. |
@Mikolaj I can confirm that the same thing happens when just using |
Well done. Thank you. |
haskell/process#273 is closed by haskell/process#277. Can we close this one? @ulysses4ever pinging you as you reopened this ticket. |
Sorry, this was my bad, probably |
Describe the bug
On Windows, when cabal tries fetching a git repo, it hangs indefinitely, in waitForProcess:
cabal/Cabal/src/Distribution/Simple/Utils.hs
Line 783 in 96dea0f
When run for the first time, it hangs while running
"git.exe" "submodule" "deinit" "--force" "--all"
; if cabal is killed, on subsequent runs it hangs on"git.exe" "fetch"
.Running the git command manually in the corresponding working directory does not hang (and after doing so, cabal builds the package successfully).
To Reproduce
Steps to reproduce the behavior:
The last line logged before cabal hangs should be
"C:\Program Files\Git\cmd\git.exe" "submodule" "deinit" "--force" "--all"
, or the equivalent with a different path togit.exe
.Expected behavior
It should build the package successfully
System information
The text was updated successfully, but these errors were encountered: