file resource limit reached on OSX when generating docs for GHC

[cartazio]

see https://ghc.haskell.org/trac/ghc/ticket/11956

[cartazio]

another (unrelated issue?) is the missing link destinations for a whole mess of things, do those correspond to module recursions and/or .hs-boot definitions?
makerun-warnings.txt

[cartazio]

see https://github.com/haskell/haddock/files/226599/makerun-warnings.txt (attached file link) for the warning outputs regarding links

[mpickering]

I have also run into this and know where to fix it.

[cartazio]

+1

It breaks the end of the haddock hyperlinekd source/doc generation for the ghc code base on mac without the ulimit intervention, so it'd be great to have this fixed before 8.0 gets cut properly :)

[cartazio]

theres a related issue in the ghc.mk file for the haddock subdir that makes it fail to copy the solarized.css and the .js that does the lovely tool tip highlighting, I hope to dig into that tomorrow, thomie gave some hints about where it might be

[cartazio]

@mpickering where does the issue lie may I ask?

[mpickering]

The fix needs to be something like this:

mpickering@04ef9d4

[cartazio]

would using something like https://hackage.haskell.org/package/base-4.8.2.0/docs/Control-Concurrent-QSemN.html make sense or not be safe?

[cartazio]

@mpickering whats that (force -> !file) ? i'm not familiar with that

[mpickering]

The intention is to force the whole file to be read into memory so the file handle could be closed. Is there a better way to do it without adding dependencies?

[cartazio]

what do you mean by dependencies?

[cartazio]

ohhh, i would probably just have the next line be something lik e

!_ <- length $! str
or something

[cartazio]

this seems to be a semi lazy io challenge in particular, or am i missing something?

[cartazio]

i've attached the shell invocation that came up in ghc that triggered the problem if you wanna try to use it to test stuff
badhaddock-invoke.txt
which should help I hope :)

[bgamari]

I think,

!_ <- return $ length str

or perhaps better,

_ <- Control.Exception.evaluate $ length str

should be perfectly sufficient, no?

[cartazio]

True

On Friday, April 22, 2016, Ben Gamari notifications@github.com wrote:

I think,

!_ <- return $ length str

should be perfectly sufficient, no?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#495 (comment)

[mpickering]

If that is the recommended way then that's fine but it always felt a bit hacky to me?

[bgamari]

Matthew Pickering notifications@github.com writes:

If that is the recommended way then that's fine but it always felt a bit hacky to me?

Indeed, this is why I try to avoid lazy IO.

[bgamari]

@cartazio do you think you could put together and test a patch for this?

[mpickering]

Ben, applying the patch I linked to earlier will fix the problem.

mpickering@04ef9d4

[cartazio]

I can test it next week, doing some fam travel so I don't have my -j10 friendly machine on me for a few days

[alexbiehl]

Fixed in e0ada17.