
It did build candidate documentation earlier for me. Not sure if something
changed recently. I always uploaded candidates, and when the documentation
was generated, I reviewed it and then published the candidate.
-harendra
On 24 January 2017 at 12:43, Gershom B
Good question!
The current incarnation of the builder doesn’t build candidate documentation — this is something we should change/implement. (Not sure if it ever built candidate documentation, actually?)
The builder itself (I just checked) is running just fine and generating documentation for fully released packages.
Best, Gershom
On January 24, 2017 at 1:22:05 AM, Harendra Kumar (harendra.kumar@gmail.com) wrote:
I am not sure if the problem has been resolved or if it has resurfaced again after getting resolved. I uploaded a package recently and the docs have not been generated even after a day. Here is the link to the package candidate that I uploaded:
https://hackage.haskell.org/package/unicode-transforms-0.2.1/candidate
Is there a place where I can see any debug logs or diagnostic messages to figure out what went wrong?
-harendra
On 16 November 2016 at 23:31, Gershom B wrote:
As an update -- the builder had a few other issues besides disk-space in terms of getting a better retry policy in place, and properly prioritizing new over older packages, etc. I think as of this morning they're finally all worked through and it seems to be slowly chugging through the backlog in a reasonable order, prioritizing new uploads.I'll be checking in on the logs daily for the time being to make sure it does't seem to be getting stuck.
If your docs haven't built and you're impatient (understandably so!), please don't bump your package version to kick the priority -- that'll just put more metadata on the server we don't need. Instead, you can build and upload your own docs as in this sample shell script:
https://github.com/ekmett/lens/blob/master/scripts/hackage-docs.sh
Best, Gershom
On Fri, Nov 11, 2016 at 11:43 AM, Gershom B wrote:
Sorry — the builder for docs has been in rough shape and we’re working on it. In this case it got stuck due to disk space issues and monitoring didn’t catch it. Its now running again but doing some catching up. (And lots of stuff in the queue it failed to build due to other problems needs to be replaced there, which is a manual process at the moment if we don’t want the queue as a whole to just drown out any new things at all with backlog). It would be much better to expose more queues and have better monitoring (and real prioritization), and another volunteer to help ben out on this would be very welcome (please contact me if you’re interested — the code lives at https://github.com/haskell/hackage-server/blob/master/ BuildClient.hs and there’s some uncommitted work on queuing as well).
—gerhsom
On November 8, 2016 at 8:37:19 PM, Patrick Pelletier ( code@funwithsoftware.org) wrote:
This is only my second time uploading a package to Hackage, so I don't yet have a feel for how it's supposed to go. I uploaded normalization-insensitive-2.0.0.1 about 24 hours ago:
https://hackage.haskell.org/package/normalization- insensitive-2.0.0.1
Under "Status", it says "Docs pending". (And the module names are all non-clickable.) Is it normal to take this long to build the docs? Is there some way to find out where in the queue my job is? Is this an indication that something has gone wrong? How do I fix it?
Thanks,
--Patrick
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.