haskell/haskell-ide-engine

How to debug hie problems?

Open

#567 opened on May 13, 2018

View on GitHub
 (17 comments) (0 reactions) (0 assignees)Haskell (2,358 stars) (205 forks)batch import
component: documentationgardening 🌱good first issuehelp wanted

Description

I'm having some difficulties getting haskell-ide-engine working under Emacs with my Nix configuration. Right now I'm facing this:

hie: <command line>: cannot satisfy -package-id aeson-1.2.4.0-G9AwmJGyHa062BMlqjD9fS
    (use -v for more information)

However, as far as I can tell, this is available in my environment, and cabal is building with this version of the library.

Is there a way to run hie so that I can try to track down where this is coming from? I'm not even sure yet how this is being triggered, since if I just run "hie" on the command-line, it doesn't report any errors, but neither do I know how to simulate whatever Emacs does when I open a Haskell file.

I'm asking here because I don't know what to do next, and I'd love to start using HIE for development. Thanks!

Contributor guide

Tech stack
None
Domain
developer experiencetooling
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Haskell toolchainNix package managerEmacs configurationGHC package management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the aeson package version mismatch. Check the Nix configuration to ensure the correct version is exposed. Look at the hie build script and the GHC package database. Review the comments in the issue for similar problems and solutions.