Haskell-ide-engine: Error relating 'stty' and cabal-helper dendency

[JorisBlanken]

Haskell Language Server Extension version 0.0.34
Visual Studio Code
Windows 10

Using the vscode extension, when opening a haskell project that is located in a folder that contains a stack project (i.e. stack init has been executed) the following issues occurs:

[Info  - 9:37:02 PM] Connection to server got closed. Server will restart.
2020-01-04 21:37:03.1001694 [ThreadId 3] - run entered for hie-wrapper(hie-wrapper) Version 1.0.0.0, Git revision a8c156b8a12d03c9eb4a23174eaac1eb9725eff1 (3539 commits) x86_64 ghc-8.6.5
2020-01-04 21:37:03.1021712 [ThreadId 3] - Current directory:d:\source\demo-project
2020-01-04 21:37:03.1021712 [ThreadId 3] - Operating system:mingw32
2020-01-04 21:37:03.1031721 [ThreadId 3] - Cabal-Helper found these projects: ["ProjLocStackYaml {plStackYaml = \"d:\\\\source\\\\demo-project\\\\stack.yaml\"}"]
2020-01-04 21:37:03.1041732 [ThreadId 3] - These projects have the build tools installed: ["ProjLocStackYaml {plStackYaml = \"d:\\\\source\\\\demo-project\\\\stack.yaml\"}"]
2020-01-04 21:37:03.1041732 [ThreadId 3] - Cabal-Helper dirs: ["d:\\source\\demo-project","d:\\source\\demo-project\\File.hs"]
'stty' is not recognized as an internal or external command,
operable program or batch file.
'stty' is not recognized as an internal or external command,
operable program or batch file.
hie-wrapper: user error (Pattern match failure in do expression at lib\Distribution\Helper.hs:603:7-22)
[Error - 9:37:04 PM] Connection to server got closed. Server will not be restarted.

I have attempted the workarounds detailed in issue #1428.
Using these workarounds simply causes the 'stty' error to dissapear, but the hie-wrapper error remains.

[jneira]

There is a bug in the starting process resolved in the last vscode extension 0.34
Updating the extension might resolve it

Afaik the stty problem only affect the output.

[JorisBlanken]

There is a bug in the starting process resolved in the last vscode extension 0.34
Updating the extension might resolve it

Afaik the stty problem only affect the output.

I'm already using the latest version of the extension.

[fendor]

Does the project build with stack, e.g. stack build succeeds? EDIT: is the project public or can you describe the test-project more?

[JorisBlanken]

Does the project build with stack, e.g. stack build succeeds? EDIT: is the project public or can you describe the test-project more?

stack build did in fact not work, resolving the issues with stack build resolved it.
Thank you!