Claudio Bley

BTW, here is a workflow run which illustrates how annoying this problem is: https://github.com/tweag/rules_haskell/actions/runs/18094346202 Of 52 CI jobs (those that make use of hackage), *26* failed because the cache was...

> @avdv Thanks for the review! Fixed and pushed. > > The `ghcide-snapshot_9.10.3.json` generation required two additional fixes in `ghcide-stack-snapshot_9.10.3.yaml`: > > 1. **Fixed resolver**: Changed from `nightly-2024-12-10` to `nightly-2024-12-11`...

I fixed a few of the remaining test failures but there are some left. Could you look into them, I probably won't be able to on the next days?!

Thank you @AlexTereshenkov! I think adding a `.bazelversion` is a bit too restrictive for a ruleset usually, since we don't want to constrain Bazel to a specific version -- it...

Hi Facundo, I took a quick look, and I saw that indeed the `-no_fixup_chains` linker option is present in `/nix/store/q2nn3dq8nyxaqngmy2s9klb2qiyzfxfx-ghc-9.8.4/bin/hsc2hs`. Also, the cc nix toolchain is configured here: https://github.com/tweag/inline-java/blob/c3a674b099d232fb9b94e558ba460d28316b7e4d/WORKSPACE#L46-L49 ```bzl...

> Not a good one. It probably was the result of copying it from elsewhere. I fixed that in the test example. CI is complaining of [a different error](https://github.com/tweag/inline-java/actions/runs/16417714026/job/46387663865) now....

Thank you for the quick reply @LeeTibbert! > To understand you use case, may I ask a few questions? > > * Is this restriction a burden? or 'just' a...

Still happens with GHC 9.6.5

Still happens on GHC 9.8.2 using bazel 6.5.0, but for [this CI run](https://github.com/tweag/rules_haskell/actions/runs/12315517094) only the nixpkgs CI job failed, the bindist one was successful: ``` ERROR: /Users/runner/work/rules_haskell/rules_haskell/rules_haskell_tests/tests/haskell_module/dep-narrowing-th/BUILD.bazel:88:16: HaskellBuildObject @//tests/haskell_module/dep-narrowing-th:lib @//tests/haskell_module/dep-narrowing-th:TestModule2...

Hi @adrien-piquerez-da, thank you for opening this issue. I see you already found a workaround, which is similar to how we have integrated `@bios` output for IDE support: ```bash bazel...