Skip to content
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

Haddocks don't build for classy-prelude-yesod #169

Open
MaxGabriel opened this issue Sep 25, 2018 · 10 comments
Open

Haddocks don't build for classy-prelude-yesod #169

MaxGabriel opened this issue Sep 25, 2018 · 10 comments

Comments

@MaxGabriel
Copy link
Collaborator

I'm pretty sure this is just a Haddock bug and you can close this, but just for awareness sake:

stack haddock classy-prelude-yesod --no-haddock-deps # no-haddock-deps to avoid haskell-src-exts using up all memory https://github.com/haskell/haddock/issues/928
Haddock coverage:
haddock: internal error: internal: extractDecl
CallStack (from HasCallStack):
  error, called at utils/haddock/haddock-api/src/Haddock/Interface/Create.hs:1097:12 in main:Haddock.Interface.Create
Completed 8 action(s).

--  While building custom Setup.hs for package classy-prelude-yesod-1.4.0 using:
      /Users/maximiliantagher/.stack/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.3 --builddir=.stack-work/dist/x86_64-osx/Cabal-2.2.0.1 haddock --html --hoogle --html-location=../$pkg-$version/ --haddock-option=--hyperlinked-source
    Process exited with code: ExitFailure 1

LTS: 12.4
OS: macOS Mojave

@snoyberg
Copy link
Owner

I agree, it's likely a Haddock bug. Let's leave it open in case (1) someone wants to implement a workaround and (2) so future reporters can find this issue.

@normenmueller
Copy link

normenmueller commented Apr 1, 2019

Is there anything new on this? Haddock still fails on classy-prelude-yesod. Any workaround, e.g., on how to exclude classy-prelude-yesod from Hoogle db generation? Otherwise my stack hoogle always fails.

@snoyberg
Copy link
Owner

snoyberg commented Apr 2, 2019

I've made no changes and don't intend to. I've generally given up on Haddock to be honest.

@normenmueller
Copy link

@snoyberg off topic: I'm also not bothered w/ Haddock too much, but stack hoogle quits in case of Haddock errors. Is there any workaround, as I'm bothered about Hoogle ;-)

@snoyberg
Copy link
Owner

snoyberg commented Apr 2, 2019

Not that I'm aware of

@normenmueller
Copy link

@MaxGabriel
Copy link
Collaborator Author

It might be this bug haskell/haddock#979

@normenmueller
Copy link

Thanks for the link. Contributing to this thread now.

@meteficha
Copy link

I've made no changes and don't intend to. I've generally given up on Haddock to be honest.

What have you been using instead of Haddock? These bugs are annoying but not having anything is worse :).

@snoyberg
Copy link
Owner

I still use Haddock when it's available. I've just spent so much time working around it that, if I don't have the Haddocks, I'll drop down to reading the source directly. It sucks, I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants