fendor

@maksbotan Can you execute, on your example project: `hie --debug src/` and link the logs?

No, it is definitely not MacOS specific. It is some kind of race that we can not pinpoint so far. As said, I can reproduce it on NixOS, but only...

@jbransen No real pointers here, yet, IIRC I was able to reproduce the problem only with `hie-bios check ` where the `filename` contained some TH. Since this project will eventually...

@andrewguy9 I think that would make sense. cc @jneira, @alanz maybe update the vscode plugin?

Same answer as here: https://github.com/haskell/haskell-language-server/issues/111 EDIT: implicit config will never (at least not right now) succeed, explicit config might work if the mentioned issue is fixed

What is the content of the generated cabal file?

Can you maybe share the project so I can try, too?

Problem is related to stack. By default test-components are not in the global project definition, and executing `stack test` enables test components. That is why `stack test` does solve that...

@prophet1906 You are running into the described problem and after running `cabal test`, the problem is solved? Do you have any special changes in your cabal project? On my test...

I would argue that cabal-helper does exactly that, in a sophisticated way and true to the original build plan. In the original build plan, some components are not active or...