-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
Error parsing targets - Directory not found
using internal (private) libraries and stack
#2041
Comments
under further investigation, I can get HLS to work on a brand new project generated with Stack. When doing an It very much points to the If anyone has any ideas that would be great othewise I'll keep digging through the Stack docs and report back as when searching for that error message I couldn't find anything online. |
Ok so the behaviour went away after I changed my
package.yaml:
and moving it's content to my cradle:
stack:
- path: "./lib"
component: "ui-data-api:lib"
- path: "./src/tsdef.hs"
component: "ui-data-api:exe:tsdef"
- path: "./src/Paths_ui_data_api.hs"
component: "ui-data-api:exe:tsdef"
I'm not sure if it's |
Thank so much for the detailed bug report and the further investigation 🙂 |
Error parsing targets - Directory not found
using internal (private) libraries and stack
@jneira ahhh I was reading that issue you linked last night and was going to report back asking if it might be related to this! As requested I tried: > stack repl ui-data-api:lib:ui-data-api-internal
Error parsing targets: Directory not found: ui-data-api:lib:ui-data-api-internal
Note that to specify options to be passed to GHCi, use the --ghci-options flag it should be Should be noted that it was happy with: > stack repl ui-data-api:lib Which all points to the support of internal libraies in stack 😞, tbh I've not really had to use them before but current projects I'm working on use them extensively |
mmm and does it work if you does a |
Oh i am just aware that |
yeah that works for me, no point in having dups 😄
which I spotted was mentioned in another stack issue that I can't seem to find! Thanks for the very prompt help, much appreciated 👍 |
Your environment
Output of
haskell-language-server --probe-tools
orhaskell-language-server-wrapper --probe-tools
:haskell-language-server version: 1.2.0.0 (GHC: 8.8.4) (PATH: /home/cmdv/.ghcup/bin/haskell-language-server-8.8.4~1.2.0) (GIT hash: be2071e985cb417f984ab00a1aad76dee02d6d0b) Tool versions found on the $PATH cabal: 3.4.0.0 stack: 2.7.3 ghc: 8.8.4
Which OS do you use: Fedora 33 - Linux
Which lsp-client do you use: Doom - emacs
Describe your project (alternative: link to the project):
./package.yml
./stack.yaml
Contents of
hie.yaml
:Steps to reproduce
stack build
which all worksExpected behaviour
Should load up and be all nice and dandy
Actual behaviour
Error outputed in lsp logs
The same error happens if running
or
view Debug output for logs. 😃
Include debug information
Execute in the root of your project the command
haskell-language-server --debug .
and paste the logs here:Debug output:
Paste the logs from the lsp-client, e.g. for VS Code
LSP logs:
The text was updated successfully, but these errors were encountered: