-
Notifications
You must be signed in to change notification settings - Fork 42
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
hdevtools can't handle cabal packages with both library and executable sections #40
Comments
Do you have a specific project this is happening on? |
I first encountered this on some proprietary code for work, but I also see the same symptoms on my small cabal test project at https://github.com/fizbin/cabal-demo-backflip Note that I can |
What is the output of |
Does seem to work with ghc 7.10 and cabal 1.22. Thanks! |
👍 |
@fizbin - I'm think maybe that's the problem you're seeing? |
Yes, sorry for the much-delayed reply. That is the issue I am seeing.
I'll look into switching to 7.10, though some of the code I'm maintaining needs to continue to compile against GHC 7.4.1, so I'll see how painful it is to be bridging both sides of the AMP. In the meantime, I do have a workaround: use hdevtools 0.1.0.6. |
Also, the exact error shown above requires that you be working in a cabal sandbox, though a very similar error (showing a bad stack of |
I can confirm this issue with 0.1.0.9. |
BTW, I’m still in a fix for 7.8 (with Cabal 1.22.1.1, if that helps). |
@nomeata - are you working on a fix? |
sorry, must have swallowed a word. I guess I wanted to write “I’m still in need for a fix for 7.8” :-] |
Starting with version 0.1.0.7, the hdevtools server will crash if asked to check a file in a
.cabal
package that has both alibrary
and one or moreexecutable
sections.On my box, I see this in the window where I start the server:
The client exits with the error message:
This does not happen in version 0.1.0.6, but happens in 0.1.0.7 and in the most recent version (0.1.0.9).
The text was updated successfully, but these errors were encountered: