-
Notifications
You must be signed in to change notification settings - Fork 842
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
Stack fails to install certain packages via stack ghci #1066
Comments
I'm unable to reproduce, and looking at the code I see the appropriate call to |
Version 0.1.5.0, Git revision 06a4b27 I386. I reproduced this several times in a row when it happened. Do you have any advice on how I can remove it from my stack workspace so I can try installing it again and confirm the same behaviour exists? Adding unbounded-delays-0.1.0.8 (which I expect would have the same issue) to my extra-deps either has no effect on HLint, or makes ghcid fail to configure. |
You can try |
This most definitely reproduces:
Didn't some idiot in #757 argue that |
Curiously, that doesn't repro on my system either :/. The thing is: we are modifying the code page for the build portion of the Line 871 in 3fa1111
Would you be able to do some tracing and see if some of the returned values in fixCodePage are not as expected? The only other thing I can think of is that perhaps the |
Tracing reveals that at Line 871 in 3fa1111
packageTargets is [] , so it never triggers the page fix. Are you literally running stack ghci ? If so, how are packageTargets being set? It may be different for me because I have run stack build in the directory first? That builds some stuff, but not the test suite, which is the thing that requires unbounded-delays .
|
Apparently hidden inside Stack.Ghci is another call to |
@ndmitchell Can you try out master now? |
Thanks, it works now. It didn't drop into |
Cool, hopefully the new placement will prevent any future problems. |
I can't install unbounded-delays via
stack ghci
, but I can viastack install
. @snoyberg, I guess you need another UTF8 fix?The text was updated successfully, but these errors were encountered: