VsCode under OSX - hie not working

[tittoassini]

Hi,

I would like to help debug vscode-hie-server under osx.

The behaviour I observe is that vscode/hie seems to work correctly, for example by detecting hlint issues, only on the first haskell file that it opens.

Afterwards, when I hover on some symbol or some hlint issue I see a 'Loading' message and nothing happens. Also code formatting does not seem to do anything.

I have installed the latest hie and vscode-hie-server from github.

I have modified hie-vscode.sh to run hie in log writing mode:
hie --lsp -d -l /tmp/hie.log | tee /tmp/hie-wire.log

I can see by the hie.log that hie continues to receive commands but the output in hie-wire.log stops shortly after startup.

The log files:
hie.log
hie-wire.log

[AlexeyRaga]

This happens to me too, but only on just a couple of projects: https://github.com/haskell-works/hw-haskell-avro is one of them.
HIE on MacOS doesn't work consistently with this project. However, I haven't (yet) investigated or looked into logs.

[k0aaa]

Did you delete the build directory after installing HIE?

[tittoassini]

On that thread I saw this comment: Note that it only makes sense to use the 8.2.2 version if your project is 8.2.2 too - ghc versions must match I recompiled my project with 8.2.2 and things seem to be improving :-) Now it seems to report issues on all files, it doesn't get stuck as before. I will keep on using it and report my findings.

…

On 20 December 2017 at 14:47, R. Patrick. Huang ***@***.***> wrote: Did you delete the build directory after installing HIE? Curretnly that causes problems. See haskell/haskell-ide-engine#400 <haskell/haskell-ide-engine#400> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABYwY-y28h5R9N3_zI-sj6afbcOjZFaks5tCQ_qgaJpZM4RIOZZ> .

-- Dr. Pasqualino "Titto" Assini http://networkpolitics.svbtle.com http://quid2.org/

[tittoassini]

BTW, if it depends on a specific GHC version, should it not do as intero that recompiles itself for every project using the current stack configuration? On 20 December 2017 at 15:45, Pasqualino "Titto" Assini < [email protected]> wrote:

…

On that thread I saw this comment: Note that it only makes sense to use the 8.2.2 version if your project is 8.2.2 too - ghc versions must match I recompiled my project with 8.2.2 and things seem to be improving :-) Now it seems to report issues on all files, it doesn't get stuck as before. I will keep on using it and report my findings. On 20 December 2017 at 14:47, R. Patrick. Huang ***@***.***> wrote: > Did you delete the build directory after installing HIE? Curretnly that > causes problems. See haskell/haskell-ide-engine#400 > <haskell/haskell-ide-engine#400> > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#36 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AABYwY-y28h5R9N3_zI-sj6afbcOjZFaks5tCQ_qgaJpZM4RIOZZ> > . > -- Dr. Pasqualino "Titto" Assini http://networkpolitics.svbtle.com http://quid2.org/

-- Dr. Pasqualino "Titto" Assini http://networkpolitics.svbtle.com http://quid2.org/

[tittoassini]

OK, so the issue was definitely due to a GHC version mismatch.
Compiling both hie and my project with GHC 8.2.2., things are fine.

All the features now seem to work, I just found this minor issue:

• hint "use newtype instead of data" is not applied when clicking on the lightbulb

However, I get a lot of these:
Got error while processing diagnostics: These modules are needed for compilation but not listed in your .cabal file's other-modules: ...

Now my cabal file is actually fine.

I guess that this is due to the fact that I have test source files in a separate test directory and that hie tries to compile them and cannot locate the src files?

Is this the issue?

How much hie actually understand of the structure of the cabal file and its different targets?

If this is actually an hie issue and not a vscode-hie-server problem, I will report it there.

[dpren]

Got error while processing diagnostics: These modules are needed for compilation but not listed in your .cabal file's other-modules: ...

👉 haskell/haskell-ide-engine#391

[nponeccop]

How much hie actually understand of the structure of the cabal file and its different targets?

Different parts of hie have different understanding. The compilation is performed by ghc-mod library which has fairly complete understanding. But for example hlint part has no understanding, so it has problems with some {-# LANGUAGE pragmas and infix operators.

I vote for closing this bug as a duplicate of haskell/haskell-ide-engine#391

[Tehnix]

@nponeccop I'll second that.

I think we can close this issue, since the original problem (mismatch between hie's GHC version and the project's) has been resolved. If you still have other issues, let's open some new specific issues for those :) (the current one being tracked in haskell/haskell-ide-engine#391)

[Rhywun]

Did you delete the build directory after installing HIE?

I was having the same problem (features like tooltips and reformatting stopped working) until I restored the build directory that I had deleted after some time. Is there some reason I have to keep the build directory around? That doesn't seem right.