3 Sep 2024 |
Hécate | nope | 13:09:38 |
fendor | What's the content of /home/hecate/.cache/hie-bios/ghc-pkg-f91714c6cd436a64e984677be6212f55 ? | 13:09:40 |
fendor | Does the same error occur when you call `haskell-language-server-9.10.1\~2.9.0.1 --debug app/Extract.hs` directly? | 13:13:29 |
Hécate | The content is:
#!/bin/sh
exec /home/hecate/.ghcup/ghc/9.10.1/lib/ghc-9.10.1/bin/ghc-pkg-9.10.1 --global-package-db /home/hecate/.ghcup/ghc/9.10.1/lib/ghc-9.10.1/lib/package.conf.d ${1+"$@"}
| 13:16:49 |
Hécate | let me see | 13:16:58 |
Hécate | ❯ haskell-language-server-9.10.1\~2.9.0.1 --debug src/GetTested/Extract.hs
Warning: nix (Nix) 2.16.1 is on the PATH (at /nix/var/nix/profiles/default/bin/nix) but Stack's Nix
integration is disabled. To mute this message in future, set notify-if-nix-on-path: false
in Stack's configuration.
Warning: Stack has not been tested with GHC versions 9.10 and above, and using 9.10.1, this may
fail.
Error: [S-6362]
No compiler found, expected minor version match with ghc-9.10.1 (x86_64-tinfo6) (based on
resolver setting in /home/hecate/.stack/global-project/stack.yaml).
To install the correct version of GHC into the subdirectory for the specified platform in
Stack's directory for local tools (/home/hecate/.stack/programs/x86_64-linux/), try running
stack setup or use the --install-ghc flag. To use your system GHC installation, run stack
config set system-ghc --global true, or use the --system-ghc flag.
All methods exhausted!
Content-Length: 203
{"jsonrpc":"2.0", "method":"window/showMessage", "params": {"type": 1, "message": "Couldn't find a working/matching GHC installation. Consider installing ghc-9.10.1 via ghcup or build HLS from source."}}
| 13:17:56 |
Hécate | now I get a stack error, despite not using stack, awesome :D | 13:18:24 |
fendor | very confusing... | 13:22:23 |
fendor | That looks correct, even though I am mad I used the literal paths | 13:25:42 |
fendor | * That looks correct, even though I am mad Iat myself for using the literal paths | 13:25:55 |
fendor | * That looks correct, even though I am mad at myself for using the literal paths | 13:26:02 |
4 Sep 2024 |
jaror | Redacted or Malformed Event | 15:57:59 |
9 Sep 2024 |
| magnolia_mayhem changed their profile picture. | 21:59:30 |
| magnolia_mayhem changed their profile picture. | 22:03:03 |
18 Sep 2024 |
fendor | HLS CI encountered some weird issues on MacOs which resolved itself a couple of days ago... Does somebody know what might have caused this, e.g., was it a GHA issue? https://github.com/haskell/haskell-language-server/actions/runs/10760272709/job/29838001624?pr=4399 | 09:16:35 |
20 Sep 2024 |
| Nadia joined the room. | 16:25:52 |
21 Sep 2024 |
| jollyrogue joined the room. | 12:38:45 |
25 Sep 2024 |
| psy1ynce joined the room. | 22:53:03 |
| psy1ynce changed their profile picture. | 23:50:19 |
28 Sep 2024 |
| @microbes:matrix.org left the room. | 09:12:16 |
1 Oct 2024 |
| @ivarsfg:matrix.org joined the room. | 10:06:34 |
3 Oct 2024 |
6d03 | is there a way to define cabal dependencies with flags? | 14:58:19 |
Hécate | In reply to @6d03:matrix.org is there a way to define cabal dependencies with flags? yes you can put a build-depends section with a flag section: https://github.com/flora-pm/flora-server/blob/development/flora.cabal#L59-L62 | 15:01:01 |
Hécate | just indent everything properly | 15:01:09 |
6d03 | ok, i know how to define cabal build flags. but i want to be able to depend on a package, with certain build option settings. for example, i may want aeson with the ordered-keymap flag disbabled. | 15:05:33 |
6d03 | ah. apparently you can specify the flag state in the freeze file 🤔 | 15:22:55 |
Hécate | ah that is what you meant, yes indeed | 15:32:25 |
| jasagredo joined the room. | 16:00:58 |
6d03 | that's not what i want though.
| 16:10:47 |
jasagredo | You can specify flags in freeze files, or in cabal.project files, but if you pull the package from somewhere else (I.e. you upload it to hackage, or someone pulls it from your github repo via source-repository-package, etc, etc) then the flag assignment will not be preserved as freeze and cabal.project files are not distributed | 17:25:49 |